The handoff stays tied to the request, reviewer action, and evidence scope instead of becoming a loose export.
Request Evidence Control for JSM
Turn JSM reviews into evidence packs.
Open a Jira Service Management request, review what proof exists, keep missing evidence visible, and export a review-ready evidence pack with receipt, manifest, source status, checksum metadata, and caveats.
Forge appRuns on AtlassianJSM ticket contextLimitations stay visible
Demo with sound
Unavailable historical group membership or source gaps travel with the pack instead of being hidden.
Receipt, manifest, source status, checksum metadata, accepted warnings, and caveats stay together.
What the review needs to prove
A closed ticket is not always enough when someone later asks what was reviewed and what could not be verified. Request Evidence Control keeps that answer in the handoff instead of leaving it in scattered comments.
Reviewed evidence
Show which available Jira and JSM records support the request before the pack is exported. Useful when another reviewer needs the request story, source status, and caveats without reconstructing the ticket later.
Visible limitations
Carry missing historical group membership or source gaps into the pack instead of hiding weak proof. The weak spot remains visible so the record does not read cleaner than the available evidence allows.
Review-ready pack
Export receipt, manifest, source status, checksum metadata, and caveats as one handoff record. The next step stays clear: what is known, what still needs review, and which action should wait.
Screenshots
Evidence handoff workflow
Follow the handoff from evidence review to visible limitations, reviewer acceptance, and an export-ready record.
Review evidence before handoff
See which requests need review, what evidence exists, and which limitation must be acknowledged before a pack moves forward.
Disclose gaps before export
Missing historical group membership remains visible so reviewers can see what could not be verified from collected sources.
Deliver review-ready packs
Pack delivery keeps the receipt, manifest, source status, checksum metadata, and preserved caveats together for review.
Operational boundaries
The app helps admins prepare a review record from available Jira and JSM evidence. It does not promise that every historical identity or group-membership fact exists in the collected sources.
Not an identity archive
Historical group membership that is not available from collected sources stays marked as a limitation. The next step stays clear: what is known, what still needs review, and which action should wait.
Not legal advice
Evidence packs support operational review and audit handoff, but customers remain responsible for their own legal and compliance decisions. The next step stays clear: what is known, what still needs review, and which action should wait.
Atlassian-hosted workflow
The Forge app uses Atlassian-hosted runtime and storage, with product support, privacy, and trust pages linked below. The next step stays clear: what is known, what still needs review, and which action should wait.
Evaluation links
Use these links when admins, security reviewers, or purchasing teams need support, documentation, or privacy and security context.