Feature #7849
open
custom issue relation types
0%
Description
In different projects I am using redmine with a number of custom trackers. To define relations between the tickets I would very much like to use other relations than the ones currently available.
For instance, we have trackers for requirements and features. And we would like to be able to define an "implements" relation: feature implements requirement.
The most sustainable solution would be to be able to define custom relation types much like custom fields. I searched for this on the redmine redmine but didn't find anything.
From looking at source:trunk/app/models/issue_relation.rb it seems fairly straightforward to factor out the relation types and define them like custom fields, including symmetry relationships between the types etc.
As we don't have any redmine development capabilities at the moment I hope more people would be interested to have that feature and somebody interested in implementing it :-) With some guidance and advise from experienced redmine developers my team might also be able to contribute to the development.
Related issues
Updated by Johan Larsson over 12 years ago
+1
Would also like to add custom issue relation types.
Updated by
Updated by Kelvin Chen almost 12 years ago
+1
Would like to have this function as well :)
Updated by 
Updated by
Updated by Mauro Chojrin almost 12 years ago
+1. In my case, we use support tickets as QA tasks. It would be really helpfull to define relations such as "Tested in" (with simmetry in "Is tested by"). This feature combined with a custom workflow woudl definitely be a great improvement of my daily workflow.
Updated by 
Updated by 
Updated by
Updated by Dipan Mehta over 11 years ago
+1. This one would be a great addition to many workflows.
Updated by
Updated by Brandon Liles about 11 years ago
+1 Definitely agree. In our organization we assign review tickets for another developer to review our work. We currently use relations to track the review ticket in relation to the work ticket, but it would be nice to have a relationship type for this.
Updated by Jeremy Thomerson about 11 years ago
+1 I just found this as well and it would be great to be able to add symmetrical relation types either by plugins, or especially through the admin UI.
Updated by Toshi MARUYAMA over 10 years ago
- Related to Feature #15340: Custom field referencing other tickets added
Updated by
Updated by Toshi MARUYAMA almost 10 years ago
- Related to Feature #16117: Add a new type of related issue: "exclusive" added
Updated by Toshi MARUYAMA almost 10 years ago
- Related to Feature #18034: related issue improvements added
Updated by Toshi MARUYAMA over 7 years ago
- Related to Feature #25384: Add new issue relation type: Obsoletes and Obsoleted_by added
Updated by Toshi MARUYAMA almost 7 years ago
- Related to Feature #26786: Complex issue relation added
Updated by Go MAEDA over 6 years ago
- Related to Feature #7629: Add "causes" and "caused by" issue relationships added
Updated by Vito Marolda over 5 years ago
+1 For this feature: our workflow would be "feature x implement request y". Anyway, a new type of custom field which accepts issues (#15340), with single or multiple choices, would also suit this need, maybe with better querying capabilities.
Updated by 
Updated by
Updated by shawn freeman over 4 years ago
+1
It looks like many of the "relationship types" have specific meanings and probably corresponding code level behaviors. I can guess that this is why this isn't already something we can configure for ourselves, like states.
I would like to suggest that the scope of this RFE be focused only on the "Related To" relationship. Specifically:- Allow the admin to define any number of aliases for "Related To".
- Present the list of "Related To" aliases in the drop-down as if they were each unique.
- Leave the underlying code behavior as-is.
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by