Edgewall Software
Modify

Opened 15 years ago

Last modified 3 years ago

#221 new enhancement

Creating TR for multiple components

Reported by: banerjed@… Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version:
Severity: critical Keywords: tracobject relation
Cc: yellen@…, franz.mayer@… Branch:
Release Notes:
API Changes:

Description (last modified by Christian Boos)

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 (29)

comment:1 by anonymous, 15 years ago

Component: generalticket system
Milestone: 0.7
Priority: normalhigh
Severity: normalenhancement
Summary: Creating TR for multiple branchesCreating TR for multiple branches & multiple components

comment:2 by daniel, 15 years ago

Priority: highnormal

comment:3 by daniel, 15 years ago

Milestone: 0.71.0

comment:4 by Christopher Lenz, 15 years ago

#336 has been marked as duplicate of this ticket.

comment:5 by Christopher Lenz, 14 years ago

#1232 has been marked as duplicate of this ticket.

comment:6 by Christian Parpart <trapni@…>, 14 years ago

Cc: trapni@… added

comment:7 by Christian Boos, 13 years ago

Keywords: tracobject relation added
Owner: changed from Jonas Borgström to Christian Boos

comment:8 by anonymous, 13 years ago

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 by Kevin Puetz, 12 years ago

This seems very similar to (though less detailed than) ticket #4298

comment:10 by Christian Boos, 12 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:11 by Christian Boos, 12 years ago

#6229 was closed as duplicate.

comment:12 by Emmanuel Blot, 11 years ago

#6867 has been marked as a duplicate

comment:13 by Christian Boos, 11 years ago

Description: modified (diff)
Severity: normalmajor
Summary: Creating TR for multiple branches & multiple componentsCreating TR for multiple components

comment:14 by elnur <elnur.home@…>, 9 years ago

This feature would be really nice.

comment:15 by Christian Parpart <trapni@…>, 9 years ago

Cc: trapni@… removed

comment:16 by Christian Boos, 9 years ago

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:17 by Christian Boos, 9 years ago

Milestone: triagingnext-major-0.1X

comment:18 by anonymous, 7 years ago

This would be very useful for us!

comment:19 by gluk47@…, 7 years ago

The usefulness of this feature does not diminish at all through the time passing…

comment:20 by anonymous, 6 years ago

One more vote from me!

comment:21 by franz.mayer@…, 6 years ago

Cc: franz.mayer@… 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 Christian Boos, 6 years ago

Severity: majorcritical

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 jmadderson@…, 6 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 anonymous, 5 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:25 by pandamasta, 4 years ago

When next-major-releases is foreseen ?

comment:26 by Ryan J Ollos, 4 years ago

Owner: Christian Boos removed

comment:27 by meredith@…, 3 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.

comment:28 by anonymous, 3 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.

in reply to:  28 comment:29 by anonymous, 3 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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set.
The owner will be changed from (none) to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.