ArtUp Labs

Guide · Jira Cloud

Suspect links in Jira: find tests that may be stale after a requirement changed

When a requirement's wording changes, the test linked to it may no longer prove it. Jira keeps the link and counts it as coverage. Here is what Jira can and cannot show you, and how to flag such links automatically.

Published 2026-10-17 · Facts checked 2026-10-17 · By ArtUp Labs, the maker of ArtUp Trace

Short answer. A link is suspect when the requirement changed after its test was linked or last reviewed: the test may no longer prove what the requirement now says. Jira does not track this. JQL cannot search for changes to a summary or description, so without an app you check the History tab of each requirement by hand. ArtUp Trace, our app, flags such links automatically.

1. Why links go stale

A test is written against a requirement as it was worded on one day. When someone later changes the requirement — "12 characters" becomes "14 characters", a new condition is added — the link stays, and every report still counts the requirement as covered. Somebody has to re-read the test against the new wording — the hard part is knowing which links to look at.

2. What Jira can tell you on its own

JQL's CHANGED operator does not apply to text fields. Atlassian's reference lists only ~, !~, IS and IS NOT for Summary. (Atlassian, JQL fields, checked 2026-10-17)

Measured On our test site on 2026-10-17, project = REQ AND summary CHANGED and project = REQ AND description CHANGED AFTER -30d were both rejected by Jira (Your query couldn't be processed), while status CHANGED AFTER -60d on the same project returned 7 work items.

What is left without an app:

  • project = REQ AND issuetype = Story AND updated >= -14d — any change at all, including status, assignee or a comment, so mostly noise;
  • then, per requirement, the History tab: did the summary or description change after the test was linked? Compare the dates with the link and with the test's last update;
  • a manual convention: a label such as needs-retest that whoever edits a requirement must add, and a filter on that label. It works as long as everyone remembers.

For a handful of requirements this is fine. For a release review of hundreds it is the part that gets skipped.

3. Suspect links with ArtUp Trace

ArtUp Trace, our Jira Cloud app, records a fingerprint of each requirement's summary and description when a link is confirmed. When either changes, every link of that requirement becomes suspect.

  • Changes to status, assignee or other fields do not make a link suspect — only the wording of the requirement.
  • On the Suspect links tab, review each link and click Confirm, or select several and Confirm selected. Confirming anchors the link to the requirement's current text.
  • The panel on the requirement shows suspect links, and they can be confirmed there.
  • Export CSV for the review record; Baselines show what changed between two snapshots — added, removed, changed text, changed links, changed status.
  • Confirming needs the Edit issues permission in the project; the app itself never writes to your issues.

When we accepted the app on our test project (25 September 2026), renaming a requirement made its link suspect, changing the assignee did not, and Confirm cleared it. The fingerprint is fixed to summary and description in this version. See the ArtUp Trace documentation and, for coverage itself, the traceability matrix guide.

Video: ArtUp Trace demo, 3:26, with captions, recorded on our test site in October 2026: coverage from the issue links you already use, suspect links after a requirement changes, and comparing baselines.

Know which tests to re-check after a requirement changes

ArtUp Trace flags links whose requirement text changed, lets you confirm them in bulk, and keeps baselines you can compare for an audit.

Get ArtUp Trace on the Atlassian Marketplace All our Jira and Confluence apps

ArtUp Trace is on the Atlassian Marketplace. Sites with up to 10 users use it free.