Edgewall Software
Modify

Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#8304 closed enhancement (duplicate)

bi-directional links between tickets

Reported by: damarkus Owned by:
Priority: normal Milestone:
Component: ticket system Version: none
Severity: normal Keywords: ticket reference bi-direction links
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

My apologies if this is already implemented, but I have googled, searched tickets, searched hacks, etc. to no luck.

I am interested in the ability to link related tickets together. I know that I can edit a ticekts 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 esablishing 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 ticekt that will show tic_2 (when looking at tic_1), and vice versa show tic_1 [when looking at tic_s]. 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-establsh 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. Understandly milestones & versions can aid in this also - but a ticket as a Prent issue for a release provides the ability to attach a deplyment schedule, contingency plans, etc to the release as a whole.

Attachments (0)

Change History (2)

comment:1 by Christian Boos, 15 years ago

Component: generalticket system
Resolution: duplicate
Status: newclosed

Hm, Google must have been down that day ;-) See google:ticket+dependencies for starting points on that topic.

Duplicate of #31.

comment:2 by damarkus <darin.markus@…>, 15 years ago

yes google must HAVE been broken that day….

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


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