Vivid Trace 1.0 Getting Started
This document describes how to install and start using Vivid Trace. To follow along, you need to be able to install the Vivid Trace add-on into a correctly-functioning JIRA system (see the Specifications for requirements), and you need to work with issues in a test project. Required time: approximately 10 minutes.
Install Vivid Trace into JIRA.
From the "Find new add-ons" administration page in JIRA, search the Atlassian Marketplace for
Vivid Trace and install it. If you can't do this, ask your administrator to do it for you. You can get a 30 day free trial of Vivid Trace, and even of JIRA itself if necessary. Detailed installation instructions are in the Add-on Administration documentation.
View the Issue Link Graph of an issue.
If you don't already have a project and some issues to use, create them now. Next, view an issue in the project, and notice that there is a "Trace" tab in the Activity sub-view of the issue. Select this tab to show the issue link graph for this issue. If there are other issues already linked to the current issue, you'll be able to see them here, according to permissions. If there are no linked issues, then the graph will show only the current issue.
Link issues together.
If you don't already have other issues to link to, create some now. Next, link the current issue to some other issues using JIRA's issue linking feature.
Summon the Link dialog by clicking on or tapping the "More" button near the top of the issue page, and then selecting "Link" from the drop-down menu.
Link to one or several issues.
Create JIRA Issue links (not Web Links) to other issues.
After creating the issue links, notice that the issues you just linked to now appear in the issue link graph. The issue link graph shows the larger context of the work that the current issue is a part of.
Navigate issues using the Issue Link Graph.
Click on any issue in the graph to instantly navigate to it. This feature enables you to quickly move to related issues across the larger unit of work, simplifying inspection and confirmation processes. The current issue is given a halo so that you always know where you are. To see all the issues in the graph in list form, click on or tap the "View issues" button.
Confirm progress and remaining work.
Try resolving several of the issues in your graph. You can do this by using the graph to quickly navigate to and resolve each of the desired issues. Notice how each issue in the graph changes its appearance to be resolved as you resolve one after the next, and from that how quickly you can judge completion of work, and how much easier this makes communicating progress to others.
To trace implementation issues back to originating requirements, start from those issues and (possibly reading left-wards) trace back to the requirements. If a given implementation issue doesn't trace back to a requirement, or the issue statuses along the trace path don't seem right, the graphs will quickly make such facts obvious.
To trace requirements satisfaction, start from the issues representing the requirements, and (possibly reading right-wards) trace towards their implementations and tests. If a requirement isn't implemented, isn't finished being implemented, or is untested, Vivid Trace's graphs will quickly make that obvious, too.