Privacy policy: Block Done While Blockers Open

Last updated: 23 October 2026

This policy covers the Jira Cloud app Block Done While Blockers Open ("the app"), published by Datadelight ("we"). Questions: privacy@datadelight.co.

What the app does

The app is a Jira workflow validator that runs on Atlassian Forge. When someone moves a work item into a status in the Done category, the app checks whether any work item it "is blocked by" is still open. If one is, Jira refuses the move and shows which blockers are open. Moves into any other status are let through without further reading.

What the app reads

• What Jira sends with each move: the work item key, the starting and destination status IDs, and the values of any fields changed during the move. The app does not use the changed field values.
• The destination status: its name and category.
• For moves into Done only, the work item's links: for each linked work item, its key, link type, current status and summary. Jira's reply also carries other basic details of each linked work item; the app does not use them.

When a move is refused, the message Jira shows the person moving the work item names each open blocker by key and status. It adds the blocker's summary only when the blocker is in the same project as the work item being moved. The summary is used for that message only: it is not stored or logged.

The condition Optional: Hide Done While Blockers Open is a Jira expression that Jira evaluates itself, as the person viewing the work item. The app's code does not run for it, and it reads, stores and logs nothing on the app's behalf.

The app reads with read-only permission (read:jira-work) and reads as the app, not as the person moving the work item. It makes no other requests: it does not read comments, attachments, descriptions or user profiles.

What the app stores

Nothing. The app has no database or storage. It keeps nothing once a move has been checked.

What the app sends elsewhere

Nothing. The app talks only to your Jira site and sends no data outside Atlassian. It has no third parties, sub-processors, analytics or cookies.

Logs

The app writes troubleshooting lines to Atlassian's Forge app logs:

• One line per move into Done: the work item key, the destination status name, whether the move was allowed or refused and why, the keys of any open blockers, and whether Atlassian reported the app's licence on the site as active, inactive or not present. Example: BCX-1 -> Done: refuse (open-blockers: BCX-2) [licence active].
• When the app's licence on the site is not active: the work item key, the destination status name and that the move was allowed because the app is unlicensed. The app then allows the move without reading the work item's links.
• When a blocker could not be read: the keys of those blockers.
• When Jira could not be read: the work item key and the error Jira returned. The app then allows the move.
• When Jira's request is missing the work item key or destination status: which of the two was missing, and the work item key and status ID if they were present. The app then allows the move.

Atlassian holds these logs. We can see them in the Atlassian developer console for 30 days. A site administrator can turn off our access to them in Atlassian Administration (Apps › Connected apps › this app › Logs access).

Personal data

The app does not store personal data. The everyday log line and the malformed-request line have no names, email addresses, account IDs or work item text.

When you uninstall

Nothing stays with the app, because it stores nothing. Lines it has already logged remain in Atlassian's Forge logs under Atlassian's log handling.

Your choices and rights

Your Jira site administrator controls the data in your Jira site. Because the app stores nothing, we hold nothing to export or erase. Send questions or requests to privacy@datadelight.co.

Changes

We will post any change to this policy at this address with a new date.