Permissions and data

Blockline is a read-only app built on Atlassian Forge. It has no servers of its own and sends nothing outside Atlassian.

Permissions

Blockline asks for two:

• read:jira-work: to read issues, issue links, fields, link types, spaces, saved filters and the viewer’s own permissions;
• storage:app: to keep its settings, saved scopes and cache in Forge storage.

It has no write permission. It cannot change an issue, a link or a setting in Jira.

Whose permissions

Every Jira read is made as the person looking at the page, so Jira applies that person’s permissions. An issue someone cannot open is never read for them and never shown to them, and Jira leaves links to it out, exactly as in Jira’s own views. That is why someone may not see a blocker a colleague can: ask the issue’s owner for access, or ask someone who can see both issues.

What it stores

Everything is in Forge storage, hosted by Atlassian:

• the site’s settings, one entry per site;
• each person’s saved scope on Apps › Blockline;
• each person’s computed views: levels, reasons, keys, summaries, dates and owner names of the issues in a view, one entry per person and view, replaced on every rebuild and served for at most 10 minutes. One person’s entries are never served to anyone else.

Storage is removed by Atlassian when the app is uninstalled.

What leaves your site

Nothing. Blockline makes no request to any service outside Atlassian, loads nothing from a CDN, and has no analytics or tracking. Its logs carry no issue content, keys or account ids.

The full policy is on the privacy page.