Allow more than one parent issue for a single issue
There are use cases where an issue can be considered a task of several parent issues.
#3 Updated by Brenton Brown about 10 years ago
Yes, I jumped the gun on that one. BUT.. to me it is interchangeable and the feature should be available for both Issues and Subprojects. Only implementing this feature for SubProjects would be counter-intuitive and infinitely less useful. (which is why this ticket was created I suppose)
#4 Updated by Vincent Gratsac almost 10 years ago
I'm really interested in using this feature. This would really help us in our use of RedMine.
I'm be available for helping on development of this feature within a patch or plug-in, but is it possible ?
It seems to me that this feature needs modifications on sql database structure...
Thanks for your work that already helps us a lot in our everyday work
#7 Updated by Jose Sun about 9 years ago
My real use case is creating Traceability Matrix table by Redmine.
Our Traceability Matrix is 3 layer: Requirement spec tracker --> Function spec tracker --> Test spec tracker.
If there is no multiple parent issue field, I have to create several Test spec tracker, which has a linkage to same test case on TestLink, under different Function spec tracker. But if Redmine has multiple parent issue field, I just create one Test spec tracker to link different Function spec trackers. It could be reduce lots of manual operation on creating redundant Test spec tracker.
#9 Updated by Dani Leni over 8 years ago
We could really use this.
We are usign Redmine for game development project.
And here is specific example:
Task Name: Draw Projectile Icons for HUD.
Parent task should be HUD and Projectiles.
So we can track % done for HUD and Projectiles since this issue is related to both components.