Setup and use

Approval Drift requires Jira Service Management Cloud requests with native approvals and a user who can read their issue and approval records. An ordinary Jira status named Approved is insufficient.

1. Open Approval Drift in Jira Apps and enter a request key.
2. Load its project policy. A project administrator selects 1–12 supported fields and saves a policy version.
3. Reload the policy. Use requests approved after the rule became effective; older approvals show incomplete policy coverage.
4. Choose Check changes. Optionally supply keys from the same project, separated by spaces or commas.
5. Read the native decision, cycle ID, source time and material event IDs. Open the native request to make operational decisions.
6. Use Read again and prepare CSV for fresh, permission-checked, copyable CSV text. No field values or approver names are exported.

Reading results

• REVIEW_REQUIRED: a protected field changed after the relevant native approval.
• NO_OBSERVED_CHANGE: no material event was found within the stated complete read and policy coverage; this is not a validity guarantee.
• NOT_APPLICABLE: no eligible approved native cycle exists.
• INCOMPLETE / UNKNOWN_BOUNDARY: evidence is incomplete, unsupported or temporally ambiguous. Do not treat it as an all-clear.
• ACCESS / STALE_RETRY / POLICY_CONFLICT: access or evidence changed. Reload and try again with an appropriate scope.

Personal reviews

Choose reviewed, needs-reapproval or no-action, and a predefined reason. Saving rereads the request and approval. These annotations are private to their author, not a shared approval log. The latest annotation is kept per approval cycle and policy version.

Delete stored app data

Load the relevant request, tick the erasure confirmation and use Erase my reviews. Repeat until the empty check is confirmed; confirmation requires two empty observations at least one minute apart. Deleted reviews are immediately hidden by a deletion marker. New saves are blocked while erasure is pending. Project administrators can erase policy configuration in batches; minimal version markers remain to prevent stale writes. Jira records are unchanged. Inaccessible records require authenticated support.

Limits

The interface accepts up to 200 keys per batch from one project, with sequential, separate source times. This is an input bound, not a performance guarantee. Evidence expires after 60 seconds; long batches and exports may require a narrower scope. Each request is bounded to 1,000 approval records, 2,000 changelog records, 100 source calls and a 20-second reader budget. Requests already in flight are not cancelled; late results are rejected. At most 128 saved policy revisions are supported per project. History reads are bounded to 200 personal review records per issue. The interface is in English.

Supported field schemas are Jira priority, due date, the standard date picker, number field and single select. Unrecognized history representations produce incomplete evidence. Attachments, comments, Assets and free-text field comparisons are excluded. No transactional snapshot or reconstruction of sensitive approved values is promised.