|Subject:||wishlist: relationships between bugs|
|Date:||Fri, 3 Sep 2010 12:05:59 +0200|
|To:||bug-App-SD [...] rt.cpan.org|
|From:||chrysn <chrysn [...] fsfe.org>|
For tracking relationships between bugs, configurable relationships between bugs would be useful. Typical use cases include: * "blocks" / "is blocked by": An n-to-m relationship useful for tracking fundamental bugs which need some issues solved before they can be fixed. This relationship might also be relevant for filtering (eg. "don't list tasks that can't be solved immediately) or when sorting bugs by relevance / votes (as those properties are carried over by this relationship). * "duplicate bug": Duplicate bugs do occur in large bug databases, and assigning duplicates is a typical task in bug tracking systems. Having the duplicate status visible in both affected bugs (and not only in the second one that is reported) is important to avoid losing additional aspects of the bug that might be reported only in the second (or subsequent) report(s). The Debian BTS, for example, knows both relationships (duplicate bugs are "merge"d there), as does bugzilla (there, being a duplicate is not a property but a resolution, and recorded in both bugs as a message).
Message body not shown because it is not plain text.