Ticket #221 (new enhancement)
Opened 8 years ago
Last modified 17 months ago
Creating TR for multiple components
| Reported by: | banerjed@… | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-0.1X |
| Component: | ticket system | Version: | |
| Severity: | major | Keywords: | tracobject relation |
| Cc: | yellen@… | ||
| Release Notes: | |||
| API Changes: | |||
Description (last modified by cboos) (diff)
Its sometimes necessary to fix a bug in both a branch release and the mainline trunk. It would be very useful to have a method by which a ticket can be assigned to multiple releases
Note: see rather #4298 for the association to multiple versions (or milestones). This ticket is focused on the association to multiple components (cf. comment:10)
Attachments
Change History
comment:1 Changed 8 years ago by anonymous
- Component changed from general to ticket system
- Milestone set to 0.7
- Priority changed from normal to high
- Severity changed from normal to enhancement
- Summary changed from Creating TR for multiple branches to Creating TR for multiple branches & multiple components
comment:2 Changed 8 years ago by daniel
- Priority changed from high to normal
comment:3 Changed 8 years ago by daniel
- Milestone changed from 0.7 to 1.0
comment:4 Changed 7 years ago by cmlenz
comment:5 Changed 7 years ago by cmlenz
#1232 has been marked as duplicate of this ticket.
comment:6 Changed 7 years ago by Christian Parpart <trapni@…>
- Cc trapni@… added
comment:7 Changed 6 years ago by cboos
- Keywords tracobject relation added
- Owner changed from jonas to cboos
comment:8 Changed 5 years ago by anonymous
- Cc yellen@… added
Has there been any thoughts or progress on this issue?
Our current workaround is to use keywords, but this requires a lot of discipline and maintenance.
comment:9 Changed 5 years ago by Kevin Puetz
This seems very similar to (though less detailed than) ticket #4298
comment:10 Changed 5 years ago by cboos
Thanks for the notice. This ticket was more suggesting a simple multiple association from one ticket to multiple milestones as well as to multiple components.
However, the association to multiple milestones has much more complex implications than the association to multiple components, as #4298 shows.
So I propose to focus this ticket more on the ticket -> n component aspect, and redirect to #4298 for the ticket -> n milestone aspect.
comment:11 Changed 4 years ago by cboos
#6229 was closed as duplicate.
comment:12 Changed 4 years ago by eblot
#6867 has been marked as a duplicate
comment:13 Changed 4 years ago by cboos
- Description modified (diff)
- Severity changed from normal to major
- Summary changed from Creating TR for multiple branches & multiple components to Creating TR for multiple components
comment:14 Changed 2 years ago by elnur <elnur.home@…>
This feature would be really nice.
comment:15 Changed 2 years ago by Christian Parpart <trapni@…>
- Cc trapni@… removed
comment:16 Changed 22 months ago by cboos
- Milestone changed from 1.0 to unscheduled
Milestone 1.0 deleted
comment:17 Changed 17 months ago by cboos
- Milestone changed from triaging to next-major-0.1X
#336 has been marked as duplicate of this ticket.