#3006: Want to be able to merge tickets
---------------------------+------------------------------------------------
 Reporter:  dcrosta        |        Owner:  jonas   
     Type:  enhancement    |       Status:  reopened
 Priority:  low            |    Milestone:          
Component:  ticket system  |      Version:  none    
 Severity:  normal         |   Resolution:          
 Keywords:                 |  
---------------------------+------------------------------------------------
Comment (by anonymous):

 As someone who administers response systems that support merge, I agree
 that option behaviour customised in config files is good:-)

 We are using Trac as both a design support tool and, with email2trac, as a
 "response centre" for product and facility maintenance. We are in the
 process of moving some of our older systems to Trac and undertaking data
 migration.

 In our existing systems that support email submission we often have
 instances where email issues are raised and then the reporter fails to
 reply to their previous contribution opening another ticket. For this
 merge is invaluable. Some users do this repeatedly.

 To be easy to follow, both suggested merge mechanisms may be ok, however:

  * If appending the ticket to be merged at the end of the remaining ticket
 with a clear token comment or rendering style indicating what was merged,
 then new comments on the ticket are added after the merged block in the
 normal style;

  * If interspersed in date-time order merged content should be visually
 different to the original ticket. It is then possible to determine which
 comments have been merged in and which were present in the original
 ticket.

 I agree that keeping the original ticket open will only confuse people.
 Most response systems I've used would changed a merged ticket to a status
 of closed and a resolution value of "merged" rather than "duplicate". I
 see no reason why merge and duplicate should not remain as for some cases
 you have a duplicate but may not be decided if it should be merged.

 Also, if possible, a statement to the effect of "merged into #xyz" on the
 ticket to be merged would be helpful.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/3006>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets

Reply via email to