ArtUp Trace documentation
In short: tell ArtUp Trace which issue types are requirements and which verify them. It then shows which requirements have no verification, flags links that went stale after a requirement changed, and lets you compare snapshots of your requirements over time. It only reads Jira and never changes your issues.
1. Set up in one minute
- Install ArtUp Trace from the Atlassian Marketplace.
- Open a project and choose ArtUp Trace in the project navigation.
- Open the Settings tab (project administrators and Jira administrators).
- Choose the requirement issue types (for example Story or Requirement) and the verification issue types (for example Test or Task).
- Optionally limit which link types count as coverage. Empty means any link type counts.
- Click Save. The first sync runs in the background; on large projects it can take up to an hour. Results appear as it runs.
No new issue types, custom fields or workflow changes are needed. ArtUp Trace uses the issue links you already have.
2. Coverage
A requirement is covered when it is linked to at least one issue of a verification type through a counted link type. The Coverage tab shows the coverage percentage, summary cards and the list of requirements without verification. Search by key or summary, sort the columns, and click a key to open the issue.
3. Suspect links
When a requirement's summary or description changes after its link was confirmed, the link becomes suspect: the verification may no longer match the requirement. Changes to status, assignee or other fields do not make a link suspect.
On the Suspect links tab, review each link and click Confirm, or select several and click Confirm selected. Confirming anchors the link to the requirement's current content. Only rows visible after your search are confirmed.
4. Baselines and compare
A baseline is a named snapshot of all requirements in the project: their content, links and status at that moment. Create one on the Baselines tab (for example before a release or an audit) and click Refresh until its status is Complete.
To compare, choose a Before and an After baseline and click Compare. Each difference is one of:
- Added / Removed — the requirement exists in only one baseline;
- Changed — its summary or description changed;
- Links changed — links were added, removed or retargeted;
- Status changed — only the status is different.
5. CSV export
Export CSV is available for requirements without verification, suspect links and baseline comparisons. The file downloads directly to your computer (UTF-8, opens correctly in Excel and Google Sheets). Very large exports are capped; the app tells you when only part of the rows was saved.
6. Issue panel
On a requirement, the ArtUp Trace panel shows whether it is covered and lists its trace links with their status. Suspect links can be confirmed right there. On issues that are not requirements, the panel says so.
7. Who can do what
| Action | Required Jira permission |
|---|---|
| View coverage, suspect links, baselines, issue panel; export CSV | Browse projects |
| Confirm links, create baselines | Edit issues |
| Change settings | Administer projects, or Jira administrator |
ArtUp Trace checks your Jira permissions for the project on every action.
8. How data stays up to date
ArtUp Trace listens to issue and link changes and updates within a few minutes. An hourly background check catches anything missed. Changing which issue or link types count starts a full re-sync automatically.
9. Languages and theme
The app follows each user's Jira language (all 26 languages Jira supports) and the light or dark Jira theme.
10. FAQ
Does ArtUp Trace change my issues? No. It only reads Jira. Confirmations and baselines are stored by the app itself on Atlassian's infrastructure.
Where is my data stored? Is personal data stored? Only on Atlassian (Forge), with no external servers. No names, emails or account ids are stored. See Privacy and Security.
The numbers look outdated. Wait a few minutes after a change, then reload the page. If the issue persists, contact support.
I cannot open Settings. You need the Administer projects permission for that project, or to be a Jira administrator.