Skip to content
Dangel Studio
de en

Handoff Receipt

Who held this issue, how long, and in which status it changed hands, straight from the issue history.

Jira Cloud · in Marketplace review

Listing still under review. Handoff Receipt is built, tested and deployed to production; the Marketplace listing is currently with Atlassian. That is why there is no install link here yet. The documentation on this page already describes what will ship. Write to me if you need earlier access.

What it does

“Who actually had this ticket, and when?” Jira’s changelog knows, but nobody enjoys reading it: assignee changes, status changes and timestamps are scattered across dozens of entries. Handoff Receipt turns them into a clean handoff trail right on the issue:

  • Full handoff trail, newest first: who passed the issue to whom and when, computed live from Jira’s own history.
  • Holding time per person, in full days: completed days are counted, never rounded up.
  • Status at every handoff, with historical names: status names come from the changelog itself. Renamed or deleted statuses appear exactly as they were called at the time.
  • Current holder read from the issue, never guessed: the app reads who holds the issue from the issue itself; if the visible history cannot explain the holding time, the panel says exactly that instead of estimating.
  • Zero storage: the changelog is the single source of truth. The app persists nothing.
Real Jira: the handoff trail on issue XGC-3
Fig. 1 Real Jira: the handoff trail on issue XGC-3

Getting started

  1. Install the app for your Jira Cloud site from the Atlassian Marketplace listing.
  2. Open any issue and show the Handoff Receipt panel via the issue’s app actions.
  3. Read the trail: the current holder with holding time on top, every handoff with its status below. No setup required.
The full handoff trail of an issue, newest first
Fig. 2 The full handoff trail of an issue, newest first
The current holder is never guessed: it comes from the issue itself
Fig. 3 The current holder is never guessed: it comes from the issue itself

Permissions and data

Handoff Receipt runs entirely on Atlassian Forge and requests exactly one permission:

  • read:jira-work: read-only calls executed with your own permissions (asUser) and scoped to the single issue whose panel you opened: the app pages that issue’s changelog (up to 300 entries) and reads the issue itself (created date, assignee, status), so the current holder always comes from the issue, not from a derivation. The trail is computed in memory and rendered immediately.

No writes to Jira, no background jobs, no scheduled scans, and no storage of any kind: the app persists nothing, not even account ids; the people shown are read live from Jira at render time. There is nothing to delete, export or leak. No external servers, no data egress, no AI, no tracking, no third-party services.

Zero storage, zero setup
Fig. 4 Zero storage, zero setup

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

  • In preparation: the app is fully built, deployed to production and verified end-to-end; the Marketplace listing is being prepared and will be linked here once Atlassian approves it.
  • Scope of this version: up to 300 changelog entries per issue; on longer histories the panel reports the count as a lower bound instead of claiming completeness.

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 Handoff 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.