[Kolab-devel] [issue4630] Roundup issues vs. merges

[Christoph Wickert]

Taken from http://wiki.kolab.org/Requirements_of_an_Issue_Tracker#Merges_and_Issues

The concept of "Merges" and "Issues" doesn't work. Jeroen opened
https://issues.kolab.org/issue4489 for the patch that already existed in
https://issues.kolab.org/merge33. Thomas then "turned the issue into a merge"
(quote Thomas) by closing the issue, creating a comment that links to the bug
and copying the nosy list. This is nether a defined workflow nor a relationship
that can be searched. Having different templates when filing a merge and a bug
is nice, but many bugtrackers offer that. Once the bug is filed all fields
should be the same, so it is actually possible to turn an issue into a merge.

    Then everything should become an Issue again and merge issues have a
corresponding keyword or something like that. OK? 
    ThomasAH 11:22, 6 October 2010 (UTC)

----------
assignedto: thomas
keyword: roundup
messages: 26835
nosy: bernhard, jmeeuwen, thomas, wickert, wilde
priority: bug
status: chatting
title: Roundup issues vs. merges

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4630>
______________________________________