Reviewed evidence
Show which available Jira and JSM records support the request before the pack is exported. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
JSM evidence handoff
Request Evidence Control for JSM.
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
Demo
The Marketplace demo shows the core workflow: open the JSM request, review Maya Chen's evidence, carry forward the group history limitation, accept the constrained handoff, and export the pack.
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.
Visible limitations
Carry missing historical group membership or source gaps into the pack instead of hiding weak proof. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Review-ready pack
Export receipt, manifest, source status, checksum metadata, and caveats as one handoff record. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Screenshots
Evidence handoff workflow
These are the same approved screenshots used for the Marketplace listing highlights.
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. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Not legal advice
Evidence packs support operational review and audit handoff, but customers remain responsible for their own legal and compliance decisions. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Atlassian-hosted workflow
The Forge app uses Atlassian-hosted runtime and storage, with product support, privacy, and trust pages linked below. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Evaluation links
Use these links when Marketplace reviewers or customer evaluators need support, documentation, or privacy and security context.