[#76] - Issue relations
- Closed
- 29 Apr 2013
- Medium
- Build: master
- # 76
One of the things I really miss on the jcode tracker is the ability to mark an issue as duplicate and include a link to the original issue without scrolling down the comments..
So I thought we can implement a simple 1:1 relation management. Example:
- Let's say
#3is a duplicate of#2
Edit #3 select "duplicate" and fill in the id of the original issue:
The "issue view" now indicates that #3 is a duplicate of #2:
While the item view of #2 indicates, that it has duplicated items #1 and #3 (while #1 is already closed)
I also added the relation types "related to" and "not before".
Open for comments.
That's a pretty good idea I believe. Obviously it will require a lot more thinking and # of code but we should keep that in mind. Also a batch update would be nice.
In the meantime I add some code to play with ;)
Cool idea, Nikolai! Looks great!
I like ZenDesk's merge feature as well. Might be more work now, but less work later when JBS is trying to manage all the tracker items.
Hello,
i have test this feature and it´s works for me very well. Nice feature! ;)
This is still open, has this been resolved with the recent commit?
Well it wasn't really an issue, but more an enhancement ;)
Since it is already committed it could be closed - unless there are more enhancements or comments.
We might re-implement that later
-
I love the idea of this. However, I'm wondering if it would make more sense to simply 'merge' the two together into a single record. It might be a bit like how Zendesk merges tickets.
I'm not sure how the implementation would work if we're using Github issues. Perhaps it would close the two distinct issues, and then add references to third which contains all the information from the other two? Merging might be too advanced, so I'd be fine with doing the 'duplicate' tracking like you have if merging turns out to be a bad idea.