Edgewall Software

Opened 20 years ago

Last modified 3 months ago

#221 new enhancement

Creating TR for multiple components — at Version 13

Reported by: banerjed@… 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 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)

Change History (13)

comment:1 by anonymous, 20 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, 20 years ago

Priority: highnormal

comment:3 by daniel, 20 years ago

Milestone: 0.71.0

comment:4 by Christopher Lenz, 19 years ago

#336 has been marked as duplicate of this ticket.

comment:5 by Christopher Lenz, 19 years ago

#1232 has been marked as duplicate of this ticket.

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

Cc: trapni@… added

comment:7 by Christian Boos, 18 years ago

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

comment:8 by anonymous, 18 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, 17 years ago

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

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

#6229 was closed as duplicate.

comment:12 by Emmanuel Blot, 16 years ago

#6867 has been marked as a duplicate

comment:13 by Christian Boos, 16 years ago

Description: modified (diff)
Severity: normalmajor
Summary: Creating TR for multiple branches & multiple componentsCreating TR for multiple components
Note: See TracTickets for help on using tickets.