Skip to content
Dangel Studio
de en

Reopen Receipt

Track every reopened issue, record the reason, and turn rework into retro data.

Jira Cloud · Version 2.0.0 · on the Atlassian Marketplace

Install from the Atlassian Marketplace

Free of charge. Installation and licensing run through Atlassian.

What it does

Every team knows the moment: a ticket that was Done comes back. Jira records the transition, but not why it happened, and nobody counts how often. Reopen Receipt turns those moments into data your retros can use:

  • Automatic capture: the instant an issue leaves the Done status category, the app writes a receipt: timestamp, from/to status, straight from the changelog. No manual steps.
  • One-click classification: on the issue panel, anyone can record the reason (regression, incomplete acceptance, or scope change), plus an optional short prevention note.
  • Retro-ready counts: the panel shows the receipt history and reason totals per issue, so patterns surface instead of vanishing into the changelog.
  • Works with custom workflows: detection uses Jira’s status categories, not status names, so Scrum, Kanban and custom workflows all work unchanged.
A reopen without a recorded reason: the receipt is waiting
Fig. 1 A reopen without a recorded reason: the receipt is waiting
All reopens classified and counted
Fig. 2 All reopens classified and counted

Getting started

  1. Install the app for your Jira Cloud site from the Atlassian Marketplace listing.
  2. Reopen any completed issue: the receipt appears automatically on the issue panel.
  3. Click a reason to classify the reopen; add a prevention note if you want the retro to remember it.
How it works: work comes back, reason, retro data
Fig. 3 How it works: work comes back, reason, retro data

Permissions and data

Reopen Receipt runs entirely on Atlassian Forge and is built for a minimal footprint:

  • storage:app: persists receipt records and classifications per issue in Forge storage
  • read:jira-work: reads the issue’s status and changelog to detect reopens; strictly read-only, scoped to the single issue involved

No write access to Jira, no external servers, no data egress: your data never leaves Atlassian infrastructure. The app stores no personal data at all: reopen authors are shown live from the Jira changelog at render time and are never written to storage. Uninstalling removes the stored data in accordance with Atlassian’s Forge data lifecycle. No AI, no tracking, no third-party services.

Support

Direct line to the developer: no ticket system, no first-level filter.

Support is provided on a best-effort basis. No fixed response or resolution times (SLA) are promised.

Status and versions

  • 2.0.0: first public release, available on the Atlassian Marketplace.
  • Captures, classifies and counts reopens per issue; reason list: regression, incomplete acceptance, scope change.

Legal

License: the end-user license agreement (standard EULA) shown on the Atlassian Marketplace listing applies; Atlassian presents it during installation. Privacy: Atlassian apps privacy policy, with a dedicated section on Reopen Receipt; the short version is in “Permissions and data” above. The app is not intended for covert employee monitoring or automated performance evaluation; see the privacy policy for details.