The app checks Jira’s own permissions. When it cannot tell whether a user has a permission (for example, Jira does not answer), it treats the answer as no. The one exception is the workflow validator, which lets a transition through when it cannot read the issue.
| Action | Who can do it |
|---|---|
| Open the admin page and use any of its actions (Self-Check, recalculation, Service Info, Migration from Connect) | Jira administrators |
| Create, edit, delete or list checklist templates | Jira administrators |
| Create fields and configure field contexts (Date of last transition, SLA breach time, ToDo List settings) | Jira administrators, through Jira’s custom field settings; the app lists the site’s statuses and SLA fields for these forms only to Jira administrators |
| Add the workflow validator to a transition | Whoever can edit the workflow in Jira; the list of ToDo List fields in its form loads only for Jira administrators, others see a message and can still save All ToDo List fields |
| See calculated values | Anyone who can see the issue |
| See a checklist in the ToDo List panel | Users with Browse projects on the issue |
| Edit a checklist in the field | Users who can edit the issue in Jira |
| Edit a checklist in the ToDo List panel, or tick an item in its list | Users with Edit issues on the issue; the panel shows Edit and enabled checkboxes only to them, and the app checks again when they save or tick |
Read a checklist through the REST API (GET /todo/items) |
Users with Browse projects on the issue, through an integration granted Read ToDo lists |
Replace a checklist through the REST API (PUT /todo/items) |
Users with Edit issues on the issue, through an integration granted Update ToDo lists |
| Find issues with the ToDo List JQL functions | Anyone; results contain only issues the user can see |
The REST API endpoints work only on ToDo List fields of this app: they cannot read or write any other custom field.
What the app may access in Jira
On installation, the site administrator approves these permissions: read Jira work items, users, issues, projects, components, fields and field context configuration; write field context configuration (used when settings arrive from Jira Data Center); write the app’s own field values; edit Jira work items on behalf of a user (a checklist saved in the ToDo List panel is stored in the name of the user who saved it, so the issue history shows who changed it); app storage; and personal data reporting (see Personal data).
The app’s screens also ask to apply inline styles: the Atlassian design components they are built from add their styles to the page as they render. This gives no access to data.

