Issue relationships - Printable Version +- Renegade Projects Network Forums (https://forums.renegadeprojects.com) +-- Forum: Inject the Battlefield (https://forums.renegadeprojects.com/forumdisplay.php?fid=60) +--- Forum: News from the Battlefield (https://forums.renegadeprojects.com/forumdisplay.php?fid=20) +--- Thread: Issue relationships (/showthread.php?tid=1681)

Issue relationships - Renegade - 29.09.2010 Since we recently had an episode of several requests succeeding each other as the "current" version of the actual request, I've looked into relationships and their customization options, and will make a few changes to the tracker. For one, I finally got the relationship graphs running, allowing you an actual "overview" of how exactly a given issue is related to other issues on the tracker. For #221 "Trenches", that looks like this:     Secondly, I will add a few new relationships - currently planned are "is tracking bug of"/"has tracking bug" "is update of"/"has update" "is blocker of"/"is blocked by" "is requirement of"/"requires" feel free to suggest more. Unfortunately, it doesn't seem like I can give normal users the right to set relationships, but even for passive consumption, the new relationships should make the web of issues clearer to understand. DCoder edit: you accidentally a whole verb. RE: Issue relationships - Renegade - 02.10.2010 Thank you very much for your input, everyone. New relationships to be used in the future are: "is component of" → "has component", for issues which are split into multiple issues "is update of" → "has update", for issues which completely replace previous issues "requires implementation of" → "is requirement of", primarily for feature requests, where a feature request relies on the functionalities requested in a different issue, but is not a direct child/expansion of said request "makes obsolete" → "made obsolete by", for situations where the implementation of one issue results in another issue no longer being required