Possible to merge tickets?
This seems like pretty straight forward but I can't seem to find the way to do it. Some advice?
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Rick on 11 Oct, 2008 07:31 PM
There is no ticket merging function in Lighthouse.
2 Posted by Travis Bell on 13 Oct, 2008 02:28 AM
Hey Rick,
Thanks. You guys planning on implementing it?
3 Posted by Will Duncan on 14 Oct, 2008 06:24 AM
At this point in time, it's not likely that it will be a feature in the near future. Demand has been pretty low for it. Common requests for it come from users who use Lighthouse as a support based system, something we have plans for in the near future to separate from Lighthouse.
4 Posted by Seth Willits on 29 Jan, 2009 06:32 AM
It's something I was just looking for as well. I use it as an internal bug tracker, not a support system. Still, sometimes duplicate tickets happen.
5 Posted by Dan Moore on 03 Feb, 2009 09:09 PM
Indeed, duplicate tickets do get created, and that is a common situation that needs to be handled by a bug tracking system.
Right now, we handle it in LH where I work by creating a new closed ticket status of "duplicate" (though we could use "invalid"), and then when closing the ticket, put in a link to the other ticket. Having all bugs (even duplicate ones) be trackable is important, that's why we don't just delete that bug. That bug number might have ended up in a document sent to a client, and when they ask for an update, we need to be able to find it again.
We do it manually that way, because that's all we can do in LH. It works OK, but handling it in a more automatic way is something people would expect from a bug tracking system.
Merging tickets is one way to do it, though of course you need to be able to have the merged ticket found by either of the original bug IDs (or URLs). This is probably the best way to do it.
You could also keep them as separate tickets, but have a relationship between the two. This would likely result in something similar to the manual process I mentioned above, with the advantage that the duplicate ticket relationship could be followed using the API. Maybe other things like status changes could be sync'd between the two or have people following either ticket automatically follow both, but that would start to get complicated and likely confusing.
6 Posted by Travis Bell on 03 Feb, 2009 09:56 PM
My main problem is that the original user would have to go back in and re-watch the "proper" ticket. If we had proper merging these users would all get subscribed to the right ticket and would make this process incredibly simple.
brandi closed this discussion on 29 Jun, 2012 10:06 PM.