How to baseline requirements in Jira

By Jake Marsh · Updated

To baseline requirements in Jira, install Tracestitch, open Requirements in the space's sidebar and go to the Baselines tab. Enter a name such as "Release 3.5 sign-off", pick the Scope (the whole space or one folder) and click Take baseline. Tracestitch freezes the ID, version, text, status, folder and trace links of every requirement in scope. Later, pick it under Compare to see what was added, changed, removed, moved or re-traced since.

Why Jira needs help here

Jira keeps a history of each field on each work item, but it has no way to freeze a set of work items at a point in time and compare that set with today. A filter shows what the requirements say now, not what they said when the release was signed off. Exporting a CSV of the filter on sign-off day gives you a file, but comparing two of those files by hand misses wording changes inside long descriptions. A baseline keeps the full text, so a compare can show the exact words that changed.

Steps

  1. Set up requirements first. A space admin turns on tracking in Requirements > Settings and picks the work item types and ID prefix. See how to create a traceability matrix in Jira for that part.
  2. Open the Baselines tab in Requirements.
  3. Under Take a baseline, type a Name. Use something you'll recognise in a year: a release, a review meeting or a contract milestone.
  4. Pick the Scope. Whole space, or one folder (its subfolders are included).
  5. Add a Note (optional), for example who approved it.
  6. Click Take baseline. It appears in the list with View, CSV and, for space admins, Delete.
  7. To compare, go to Compare. Pick a baseline under From baseline, then Current requirements or another baseline under To, and click Compare.
  8. Read the result. A summary shows how many requirements were added, changed, removed and re-traced. Each row shows the change: a version jump such as "v2 to v4", a status change, a move between folders, or links added and removed. Click Text changes on a changed row to see the old and new wording, with added words in bold and removed words struck through. Tick Show unchanged to list everything.

What a baseline keeps

KeptNot kept
Requirement ID and work item keyComments and attachments
Version number and full text (summary, description, extra text fields you chose)Fields that aren't part of the requirement text, such as priority or assignee
Status and folderChanges made after the baseline was taken
Trace links: implementing work, tests, defects, related requirements

A baseline is read-only. Editing a requirement afterwards creates a new version and leaves the baseline as it was.

Showing a baseline in Confluence

If Tracestitch is connected to Confluence on the same site, insert the Requirements (Tracestitch) macro on a page. Enter the requirement IDs or work item keys, separated by commas, and type the baseline name in Baseline. The page then shows those requirements as they were in that baseline, even after they change in Jira. Leave Baseline empty to show the current version. Under Content, choose Show the requirement text or ID, title and status only. Readers see a requirement only if they can browse it in Jira, and the macro sits in its own block, so it never edits the text around it.

Limits

  • Up to 1,000 requirements per baseline and 200 baselines per space.
  • CSV on a baseline gives up to 1,000 rows, as text you copy into a spreadsheet or a .csv file.
  • Anyone who can edit work items in the space can take a baseline. Only space admins can delete one.

What it costs

Tracestitch is $10 a month for up to 10 users. From 11 users, every user is billed at $2.05 a month, with lower rates on larger sites. Atlassian bills it and there's a free trial. Pricing and the install link are on the Tracestitch page.

Tracestitch: Requirements and Traceability for Jira

Requirement IDs, versions and readable diffs on Jira work items. Baselines, a traceability matrix and suspect links after changes. From $10 a month for up to 10 users.


Questions

Can I compare two old baselines with each other?

Yes. Pick one under From baseline and the other under To.

Does a requirement deleted after the baseline still show in it?

Yes. A deleted requirement is retired, not erased, so View on the baseline still lists it with its frozen text.

Can I baseline only part of the space?

Yes. Pick a folder under Scope. Subfolders come along.

Can I take a baseline of work items that aren't requirements?

A baseline covers requirements. Their linked stories, tests and defects are recorded as trace links, but those items' own text isn't frozen.


More Tracestitch guides


More Jira guides