Jira Service Management · Read-only comparison
Review changes between submitted forms and Jira.
Compare linked numbers, dates and explicitly enabled short text. Keep submitted snapshots intact while recording the differences your team has reviewed.
Release in preparation. Not yet approved or available to buy.
Make the comparison explicit
Preserve submitted snapshots by default, require a current match for a selected field, or exclude a field. Administrators save versioned rules for the project.
Keep a review record
Save observation metadata and an internal review reason. A changed source or rule version invalidates an earlier acknowledgement. An acknowledgement is not a native approval or a repair.
Check a bounded list
Review an explicit list of visible issues. The app stops at its request/time budget and identifies partial coverage. Discovery accepts at most 200 issues; this is not a promise that all 200 can be reviewed in one run. Each issue can contain at most three forms and each form at most forty questions.
Data boundaries
Source values stay out of app storage. Forge stores rule versions and minimal review metadata; observations and acknowledgements expire after 30 days. Choices, rich text, external data connections and conditional visibility are not evaluated. No Jira writes, scheduled scans or external AI.