Reference
Permissions, data, licensing
Who can do what
| Action | Who |
|---|---|
| Open sessions and sort issues | Anyone who can browse the project |
| Create a session | Anyone who can browse the project |
| Reveal, choose final values, write to Jira, reopen, delete | The person who created the session, and Jira administrators |
Issues are read with each person's own Jira permissions, and estimates are written with the facilitator's permissions. The app cannot show or change anything you could not see or change yourself.
What the app stores
- Sessions: name, JQL, scale, target field, the IDs of the issues, the final values, and the Atlassian account ID of the facilitator.
- Votes: for each person, their Atlassian account ID and which column they chose for each issue.
Everything is kept in your site's Atlassian Forge storage. Issue summaries and names are read from Jira when the page opens and are not stored. Nothing is sent outside Atlassian.
Personal data
Account IDs are personal data. The app reports the IDs it keeps to Atlassian every week, as Atlassian requires, and deletes the votes of accounts that were closed. Deleting a session deletes all its votes.
Permissions the app asks for
| Scope | Why |
|---|---|
| read:jira-work | Find the issues with your JQL and show them |
| write:jira-work | Write the final estimates to the field you chose |
| read:jira-user | Show the names of the people who sorted |
| storage:app | Keep sessions and votes |
| report:personal-data | Atlassian's weekly report on stored account IDs |
Licensing
Free for up to 10 users. Larger sites pay through the Atlassian Marketplace. If a licence lapses, sessions stay readable but cannot be changed until it is active again.