Privacy notice: Blocker Fields for Jira

Effective 2026-09-21. Publisher: Sidecar Tools (support@sidecartools.com).

What the app reads. For each work item: its issue links (link type, and the id and status of the linked work item), plus the site's field list, using the read:jira-work scope. It does not read summaries, descriptions, comments, attachments or people.

What the app writes. Four app-owned custom field values on work items (write:app-data:jira): Blocker count, Open blocker count, Blocks count and Open blocks count.

Where data lives. Entirely inside your Atlassian site. Field values are stored by Jira as issue fields. The app stores only its own field ids and a backfill timestamp in Forge Key-Value Storage (storage:app). Nothing is sent outside Atlassian's infrastructure; the app has no external egress and no servers of its own. The app logs counts only.

Personal data. None. The four values are numbers.

Who can see the fields. The same people who can see the work item that carries them. Note: the counts include linked work items the viewer may not be able to see (for example a blocker in a project they cannot browse). The count reveals that such a link exists and whether it is open, but nothing else about the linked work item.

Retention. Values remain on work items until the app is uninstalled; uninstalling removes the fields and their values per Jira's handling of app-owned fields.

Analytics and tracking. None.

Contact. support@sidecartools.com.