[MDEV-12949] Visualization of issue links and dependencies in JIRA Created: 2017-05-30 Updated: 2018-09-02 Resolved: 2018-09-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | N/A |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Keiei Tanto | Assignee: | Rasmus Johansson (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Greetings! May I propose evaluating an issue dependency visualization tool: Vivid Trace for JIRA Atlassian Marketplace: https://marketplace.atlassian.com/plugins/vivid.trace/ We make this tool, and one of our production goals from the very start is to support OSS projects, particularly ones tied to the successes in our careers like MySQL / MariaDB. JIRA doesn't include issue link visualization, but according to the results of the JQL query "issue in hasLinks()", 4810 of the 13651 issues visible to me on this JIRA instance, or approximately 35%, have issue links, and 1184 of those are unresolved. With Vivid Trace, users will be able to quickly understand transitive issue dependencies and get more mileage out of this under-utilized issue linking function in JIRA with all sorts of benefits. Particularly to see blockers, blocked issues, root causes, nests of duplicates for quick resolution, for tracing chains of events, traceability on Epics, and so on and so forth. In terms of an evaluation, you might like to compare and contrast alternatives, such as:
Vivid Trace is designed in part to support OSS projects:
Some of us have contributed code to MySQL and now MariaDB (collation and locale work, back in the teething days), we also shipped MySQL in several commercial products. So we have benefitted tremendously. And now we would be honored if our issue dependency visualization tool can be of service to the community. |
| Comments |
| Comment by Rasmus Johansson (Inactive) [ 2018-09-02 ] |
|
Thanks for the suggestion, but this is currently not a priority. |