[Trac] Re: bi-directional links between tickets

2009-05-20 Thread Jeff Hammel

You might check out the TracBacksPlugin:

http://trac-hacks.org/wiki/TracBacksPlugin

Jeff

On Wed, May 20, 2009 at 07:45:27AM -0700, damarkus wrote:
 
 
 I am interested in the ability to link related tickets together. I know that
 I can edit a ticket's description and place a reference to another ticket
 there-in (or similarly in a comment), but that does not automatically link
 the target ticket back to the source ticket.
 
 Our customer uses the JIRA system for issues, and JIRA has the nice feature
 of Links - it allows establishing a link in a given ticket (i.e. tic_1) to
 another related ticket (i.e. tic_2) in a dedicated field on the ticket.
 There is then a LINK section on the ticket that will show tic_2 (when
 looking at tic_1), and vice-versa show tic_1 [when looking at tic_2]. this
 reverse linking is automatically established when the initial link is
 defined.  As the link can be initiated from either ticket, it can also be
 dropped from either ticket. There is no limit to the number of links
 to;/from a given ticket. 
 JIRA also provides the feature of specifying the TYPE of relationship
 between the tickets - i.e. Parent Of/Child of. However this additional
 information is not critical - simply having the ability to auto-establish
 bi-direction links b/w tickets is what is useful and desired.
 This can come in extremely handy in a situation where perhaps a Parent
 Ticket is created to round up Child tickets for bugs/enhancements that will
 go into a release. Understandably milestones  versions can aid in this also
 - but a ticket as a Parent issue for a release provides the ability to
 attach a deployment schedule, contingency plans, etc to the release as a
 whole.
 
 Any information on how to achieve this, or if there is a plug-in, etc would
 be greatly appreciated.
 -- 
 View this message in context: 
 http://www.nabble.com/bi-directional-links-between-tickets-tp23636870p23636870.html
 Sent from the Trac Users mailing list archive at Nabble.com.
 
 
  

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: bi-directional links between tickets

2009-05-20 Thread Greg Troxel

  Our customer uses the JIRA system for issues, and JIRA has the nice feature
  of Links - it allows establishing a link in a given ticket (i.e. tic_1) to
  another related ticket (i.e. tic_2) in a dedicated field on the ticket.
  There is then a LINK section on the ticket that will show tic_2 (when
  looking at tic_1), and vice-versa show tic_1 [when looking at tic_2]. this
  reverse linking is automatically established when the initial link is
  defined.  As the link can be initiated from either ticket, it can also be
  dropped from either ticket. There is no limit to the number of links
  to;/from a given ticket. 
  JIRA also provides the feature of specifying the TYPE of relationship
  between the tickets - i.e. Parent Of/Child of. However this additional
  information is not critical - simply having the ability to auto-establish
  bi-direction links b/w tickets is what is useful and desired.

This is basically an extension of what I am proposing to change in
mastertickets to add WBS component links.  Once there are multiple kinds
of edges in the graph, one can have blocks, is-part-of, and related, all
with different semantics.



pgpT5kv4MypBr.pgp
Description: PGP signature