Edgewall Software

Ticket #221 (new enhancement)

Opened 4 years ago

Last modified 3 months ago

Creating TR for multiple components

Reported by: banerjed@… Owned by: cboos
Priority: normal Milestone: 1.0
Component: ticket system Version:
Severity: major Keywords: tracobject relation
Cc: trapni@…, yellen@…

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

Changed 4 years ago by anonymous

  • priority changed from normal to high
  • summary changed from Creating TR for multiple branches to Creating TR for multiple branches & multiple components
  • component changed from general to ticket system
  • severity changed from normal to enhancement
  • milestone set to 0.7

Changed 4 years ago by daniel

  • priority changed from high to normal

Changed 4 years ago by daniel

  • milestone changed from 0.7 to 1.0

Changed 4 years ago by cmlenz

#336 has been marked as duplicate of this ticket.

Changed 3 years ago by cmlenz

#1232 has been marked as duplicate of this ticket.

Changed 3 years ago by Christian Parpart <trapni@…>

  • cc trapni@… added

Changed 2 years ago by cboos

  • keywords tracobject relation added
  • owner changed from jonas to cboos

Changed 19 months 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.

Changed 14 months ago by Kevin Puetz

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

Changed 14 months 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.

Changed 7 months ago by cboos

#6229 was closed as duplicate.

Changed 3 months ago by eblot

#6867 has been marked as a duplicate

Changed 3 months ago by cboos

  • summary changed from Creating TR for multiple branches & multiple components to Creating TR for multiple components
  • description modified (diff)
  • severity changed from normal to major

Add/Change #221 (Creating TR for multiple components)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.