Opened 20 years ago
Last modified 3 months ago
#221 new enhancement
Creating TR for multiple components — at Version 13
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | ticket system | Version: | |
Severity: | critical | Keywords: | tracobject relation |
Cc: | yellen@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
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)
Change History (13)
comment:1 by , 20 years ago
Component: | general → ticket system |
---|---|
Milestone: | → 0.7 |
Priority: | normal → high |
Severity: | normal → enhancement |
Summary: | Creating TR for multiple branches → Creating TR for multiple branches & multiple components |
comment:2 by , 20 years ago
Priority: | high → normal |
---|
comment:3 by , 20 years ago
Milestone: | 0.7 → 1.0 |
---|
comment:4 by , 19 years ago
comment:6 by , 19 years ago
Cc: | added |
---|
comment:7 by , 18 years ago
Keywords: | tracobject relation added |
---|---|
Owner: | changed from | to
comment:8 by , 18 years ago
Cc: | 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:10 by , 17 years ago
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:13 by , 16 years ago
Description: | modified (diff) |
---|---|
Severity: | normal → major |
Summary: | Creating TR for multiple branches & multiple components → Creating TR for multiple components |
#336 has been marked as duplicate of this ticket.