Get 24/7 customer support

Slava Shinderov  Staff  5/21/2007 6:47:56 AM

Please review Linking multiple records to one faq.

Murray Pope 12/10/2007 5:19:13 AM

Thanks very much for posting the link. I think it's precisely to avoid having to do this that this mod is being requested. Also that method assumes that there is a hierarchy which may not always be the case (though I guess you could argue about how the business process should view it, and whether implementing this mod would encourage users to create impenetrable webs of links!)

Matthew Hesse 4/16/2010 9:00:49 AM

I find that in some ways it has helped to have the restriction (in that it forced us to identify a primary ticket to which all secondary/duplicate threads should be linked, and encouraged us to incorporate or Close duplicates), but at the same time could be too restrictive if issues were related but not identical, in which case the "web" effect was both appropate and necessary (even if complicated). It's up to us (managers, admins), then to manage when it's appropriate.

This could be partly controlled by not allowing the Link function to certain user types (perhaps requiring that a link be suggested, but subject to approval by a role with higher permissions set).

Mirreza, Mehrdad 2/10/2014 6:53:24 AM

I'd like to add that having multiple links is very useful but it would be much more useful to have also a "relationship" attribute for the link.

E.g. #88888 is linked to:
- #88889 (Relation: "refines")
- #88877 (Relation: "verifies")
- #88899 (Relation: "contained by")

At the "other side" we should then have:
#88889 is linked to:
- #88888 (Relation: "refined by")

#88877 is linked to:
- #88888 (Relation: "verified by")

#88899 is linked to:
- #88888 (Relation: "contains")

This way you can build a network of tickets with different types and achieve a complete traceability.