Opened 21 years ago
Last modified 10 months ago
#221 new enhancement
Creating TR for multiple components
| Reported by: | Owned by: | ||
|---|---|---|---|
| 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)
Attachments (0)
Change History (31)
comment:1 by , 21 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 , 21 years ago
| Priority: | high → normal |
|---|
comment:3 by , 21 years ago
| Milestone: | 0.7 → 1.0 |
|---|
comment:4 by , 20 years ago
comment:6 by , 20 years ago
| Cc: | added |
|---|
comment:7 by , 19 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 , 18 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 , 17 years ago
| Description: | modified (diff) |
|---|---|
| Severity: | normal → major |
| Summary: | Creating TR for multiple branches & multiple components → Creating TR for multiple components |
comment:15 by , 15 years ago
| Cc: | removed |
|---|
comment:17 by , 14 years ago
| Milestone: | triaging → next-major-0.1X |
|---|
comment:19 by , 12 years ago
The usefulness of this feature does not diminish at all through the time passing…
comment:21 by , 12 years ago
| Cc: | added |
|---|
For our company this feature would be also very useful. Currently we use a special component "general", which marks the ticket as it effects more than one component.
comment:22 by , 12 years ago
| Severity: | major → critical |
|---|
The 1 → n problematic this ticket exemplifies has very far reaching consequences. Using "Enhancement / critical" here as a way to flag the tickets having strong impact on the design.
comment:23 by , 11 years ago
Does this feature currently exist in 1.0? I am currently trying to set this up for my company as there are quite a few scenarios where a ticket will affect more than one component of our system? Is it possible to set Component to a multi-select check box field?
comment:24 by , 10 years ago
I would use Trac if it wasnt for this being missing. Its important to be able to mark an issue as affecting multiple components, multiple releases and multiple projects. See Launchpad and The Bug Genie. For this reason I now use Bug Genie…shame. Trac looks real nice.
comment:26 by , 10 years ago
| Owner: | removed |
|---|
comment:27 by , 9 years ago
We are getting to a point where I think we'll start looking for a system to replace Trac if we can't resolve this issue with not being able to track code that is dropped in multiple releases. Reporting on this information is extremely difficult given the current feature set.
follow-up: 29 comment:28 by , 8 years ago
There are other trackers which have this feature. I'd suggest that after 12 years, either implement this our tell us all it won't happen.
comment:29 by , 8 years ago
Replying to anonymous:
There are other trackers which have this feature. I'd suggest that after 12 years, either implement this our tell us all it won't happen.
I meant the feature to select multiple components for a single ticket.
comment:31 by , 4 years ago
| Cc: | removed |
|---|
#336 has been marked as duplicate of this ticket.