Myriastra Studio

User Guide — ReqDrift for Jira

For project administrators and team members · Updated 9 October 2026

ReqDrift watches an Excel requirements table that you keep as an attachment on a Jira issue. Each time you attach a new version, it compares it row by row with the last confirmed version. After you review the changes, it marks the Jira issues that match the changed or removed rows, and the issues linked to them, so the people working on them know to check.

ReqDrift does not decide whether a change needs action; that is up to your team. A mark only says "the requirement behind this issue has changed — please check".

The screenshots on this page come from a test project, Employee Portal (key EP), whose requirements table is the issue EP-1. Select any screenshot to see it full size.

1. How it works in one minute

  1. A project administrator registers the Jira issue that holds the table.
  2. The first .xlsx attached to that issue after registering becomes the baseline.
  3. Each later .xlsx attached there is compared with the last confirmed version.
  4. Someone opens Review, unticks rows that do not matter (a typo fix, for example), and presses Confirm.
  5. ReqDrift marks the matching issues and the issues linked to them.
  6. The people on those issues check them and close each mark as Reflected or No impact.
  7. While marks are open, the person who registered the table gets a weekly email listing them.

Everything happens on the ReqDrift page of the project (open the project, then choose ReqDrift from the project's Apps menu) and in the ReqDrift panel of each issue.

2. Prepare the table

ReqDrift reads only the first sheet of the workbook.

How rows find their issues

A row is matched to issues in the table's project in up to three ways. You choose which ones when you register.

WayA row matches an issue when…
Match summary (on by default) the issue summary starts with the REQ ID (PORTAL-001 Login page) or with the REQ ID in brackets ([PORTAL-001] Login page). PORTAL-0010 does not match PORTAL-001.
REQ ID field (optional) a Jira custom field you name holds exactly the REQ ID. Text, number, select, labels and multi-select fields are supported.
Key column (optional) a column of the table holds Jira issue keys (KAN-12, or several keys in one cell).

From each matched issue, ReqDrift follows issue links one step (and parent / child), for the link types you keep on in Settings. Linked issues in other projects are included.

3. Register a table

You need the Administer Projects permission in the project.

  1. Create (or pick) a Jira issue in the project that will hold the table. Attach nothing yet.
  2. Open the project's ReqDrift page and go to Register a table.
  3. Fill in:
    • Issue key — the issue that holds the table, for example KAN-1.
    • REQ ID column header — the header text of the REQ ID column, exactly as in row 1.
    • Key column header (optional) — the header of a column of issue keys.
    • REQ ID field id (optional) — for example customfield_10050.
    • Match summary — leave it on unless you match only by key column or field.
  4. Press Register. You see "Registered. The next .xlsx attached to this issue becomes the baseline."
  5. Attach the table as an .xlsx to that issue. This first version is the baseline; nothing is marked yet.
The ReqDrift page of the project with the Register a table form filled in: Issue key EP-1, REQ ID column header REQ ID, Key column header Jira issue, Match summary on, and the message Registered. The next .xlsx attached to this issue becomes the baseline. The table's row above shows the status registered.
The project's ReqDrift page, just after registering EP-1. In this project ReqDrift is a tab across the top; where it appears in yours is decided by Jira.

At least one way of matching must be on, or registering is refused.

Registering an issue again resets the baseline: the next .xlsx becomes the new baseline, and changes since the last confirmed version are not shown. ReqDrift warns you and asks you to press Register again (resets the baseline) before it does this.

4. Attach a new version

When the requirements change, attach the new .xlsx to the same issue. Every .xlsx attached to that issue is read as a new version, whatever its name — so attach only the requirements table there. You do not need to delete the old file.

The issue EP-1, Requirements: Employee self-service portal, with two attachments: portal-requirements-v1.xlsx and portal-requirements-v2.xlsx.
The table's issue with two versions attached. The older file can stay.

The new version is read shortly after it is attached; there is no fixed time. The table's row on the ReqDrift page shows where it is:

StatusMeaning
registeredRegistered; no version has been read yet.
retryingReading failed once and will be tried again.
baselineThis version is the baseline. The next one is compared with it.
diffedCompared. Open Review.
supersededA newer version arrived before this one was finished.
req_id_missingThe REQ ID header was not found in row 1 of the first sheet. Check it in Settings, then attach the .xlsx again.
needs_settingsNo REQ ID column is set. Set it in Settings, then attach the .xlsx again.
too_largeThe file is larger than 2 MiB and was not read.
size_unknownThe size of the file could not be determined, so it was not read.
prev_unreadableThe previous version could not be read, so this version became the new baseline without a comparison.
gave_upThe version could not be read after several tries. Attach the .xlsx again.

Next to it, Facts shows whether ReqDrift has finished looking up the matching issues in Jira (collecting, then ready), and Confirm shows what happened after you confirmed.

5. Review and Confirm

Press Review on the table's row. You see each row that changed between the last confirmed version and this one:

The Review for EP-1: three Changed rows and one Removed row, each ticked with a Will mark line such as EP-3 (direct), EP-9 (linked via Relates), EP-10 (linked via Relates); one Added row, PORTAL-008, saying New requirement. No Jira issue has this REQ ID yet, so nothing is marked; and the Confirm button.
The Review. Each ticked row shows which issues it will mark, directly or through a link.

Untick any row whose change does not affect the work, such as a typo fix. Then press Confirm. To confirm you need the Edit Issues permission on the table's issue. You see "Confirmed. Marks are being applied." and, a moment later, "Marks are applied." Use Refresh to see the latest state.

The table's row showing Confirm: Marks are applied, and below it Open marks: EP-10 with A requirement linked to this issue has changed, and EP-3 with This issue no longer matches the requirements table, each with a memo field and the Reflected and No impact buttons.
After Confirm. The marks appear under Open marks on the same page.

If ReqDrift could not write to some issues, the Review says so (for example "Not written to Jira: 1 without permission."). The marks themselves are still recorded in ReqDrift.

If the Jira lookup was incomplete (for example because some issues are protected by issue security), the Review explains why and offers Acknowledge instead of Confirm. Acknowledging marks nothing; the next version is compared with this one.

If a newer version arrives before you confirm, review the newer one: it is compared with the last confirmed version, so no change is lost.

6. Marks

A marked issue gets three things:

To open the panel, click the app icon (View app actions) under the issue title and choose ReqDrift.

A marked issue: the ReqDrift panel with REQ ID PORTAL-002 and This issue no longer matches the requirements table, the label reqdrift-open in the issue details, and a comment from ReqDrift naming Requirement: PORTAL-002.
A marked issue: the panel, the reqdrift-open label and the comment.

The label and comment are written only when Write to Jira is on for the table (it is on by default). When it is off, marks are shown only in ReqDrift.

Marks are recorded by the app itself, so a linked issue in another project can be marked in ReqDrift even if the person who confirmed cannot open it. The label and comment are written to an issue only if the person who confirmed has the Edit Issues and Add Comments permissions on that issue, checked when the marks are applied. Otherwise the mark stays only in ReqDrift, and the result counts the issue as without permission. Lists and emails show only issues the reader can see; the rest are counted, not named.

If the same requirement changes again while its mark is open, the change is added to the same mark. If it changes after the mark was closed, the issue gets a new mark.

7. Close a mark

Check whether the issue needs to follow the new requirement, then close the mark:

You can add a memo (optional, up to 1,000 characters). You need the Edit Issues permission on the marked issue. You can close a mark in the issue's ReqDrift panel, or in Open marks on the project's ReqDrift page, which lists every open mark in the project that you can see.

The ReqDrift panel of the issue with the memo Expiry changed to 15 minutes. typed in, above the Reflected and No impact buttons.
Closing a mark from the issue's panel, with a memo.

The close is applied shortly after you press the button ("Close requested. It will be applied shortly."). When an issue has no open marks left, the reqdrift-open label is removed.

ReqDrift keeps a record of each closed mark. The panel shows Closed marks: N and the Last decision — the REQ ID, Reflected or No impact, the date, the memo, and who decided.

The issue EP-3 after its mark was closed: the ReqDrift panel says No open marks on this issue, Closed marks: 1, and Last decision: PORTAL-002 — Reflected in this issue on 2026-10-08 — Expiry changed to 15 minutes. The Labels field is empty again.
After the close: no open marks, the label is gone, and the last decision is kept.

8. Settings

Press Settings on a table's row. Anyone who can see the table's issue can view them; changing them needs the Administer Projects permission. Changes apply from the next version of the table.

The Settings of the table EP-1: REQ ID column REQ ID, Key column Jira issue, REQ ID field id empty, Match summary on, Write to Jira on, Watched columns Requirement and Priority, Traced link types Relates and Parent / child, and the line Changes apply from the next version of the table.
The Settings of a table. The REQ ID column and the key column (Jira issue) are not in the list of watched columns.

The settings fall into three groups. Only the first one has to be set; the defaults of the others watch everything.

Required: which column is the REQ ID

SettingWhat it does
REQ ID column The header text of the column that holds the requirement ID. It names a column, not a row: the column can be anywhere and its header can be any text, as long as the header is in row 1.

For example, with this table you would enter Req No.:

ABCD
1Req No.TitlePriorityJira
2PORTAL-001Login pageHighKAN-3
3PORTAL-002Password expiryMediumKAN-5

Matching

These are the three ways described in How rows find their issues (section 2). At least one must be on.

SettingWhat it does
Match summary Match issues whose summary starts with the REQ ID or with [REQ ID]. On by default.
REQ ID field id Optional. A Jira custom field that holds the requirement ID.
Key column Optional. The header of a column of Jira issue keys (Jira in the example above). If it disagrees with the matches found in Jira, the row is not marked.

What to mark (you can leave these as they are)

By default every column except the REQ ID column and the key column is watched, every link type is traced, and marks are written to Jira. Change these only when you want less.

SettingWhat it does
Watched columns Mark issues only when one of the checked columns changes. Untick a column whose changes do not matter (a "Last edited" column, for example). New columns are watched until you untick them. The REQ ID column and the key column are not in this list: they are used to find rows and issues, not compared as changes.
Traced link types Also mark issues connected by the checked link types (including Parent / child). New link types are traced until you untick them.
Write to Jira Add a comment and the label reqdrift-open to marked issues. When off, marks are shown only in ReqDrift.

Renaming a column header

A column is recognised by its header text, so renaming a header in the workbook is seen as one column removed and another added:

To lose nothing, rename headers in a version that changes nothing else, then update Settings to match.

9. The weekly email

While a table has open marks, the person who registered the table receives an email about it at most once a week. It lists up to 20 open marks — the issue, the REQ ID, how it was reached and how many changes it has — with a link to each issue. Issues the recipient cannot see are counted, not named.

There is no fixed day or time. No email is sent in a week when the table has no open marks, and if sending fails, that week's email is not retried. The email is sent through Jira's own notification service.

10. License

If the ReqDrift license for your site is inactive, existing marks stay visible, but new versions are not read, changes cannot be saved, and no weekly email is sent. The ReqDrift page and panel say so. Ask your site admin to renew the license.

11. Limits worth knowing

12. Getting help

Email contact@myriastrastudio.com. Please do not send your workbook or the contents of your issues; describe what you see on the screen instead. What the app reads, writes and stores is described in the Privacy and Security Policy.