Security and permissions
Jira permissions
We require certain permissions from your organization's Jira Software boards to generate development metrics that complement those derived from your Git provider activity. Understand why and how we use these OAuth scopes below:
Application scopes
Organization account scopes
| Scope | Permission | Reason |
|---|---|---|
| board | Read | List software boards from which you can choose to import issues. |
| project | Read | List the projects associated with the boards to show you a readable name and picture. |
| status | Read | List the available status IDs for issues in a given board. |
| sprint | Read | Get sprint data related to fetched issues. |
| issue-type | Read | List the types of issues your team has cofigured (e.g. 'Bug', 'Feature'). |
| issue-status | Read | Get the status name of an issue (e.g. 'To do', 'In progress', 'Done'). |
| issue-details | Read | Get issue name, type, timestamps, status history and other related details. |
Events
| Subscriptions | Reason |
|---|---|
| App installed | Detect when you install Jira. |
| Board created/updated | Detect if you should be available to start tracking new software boards. |
| Board configuration-changed | Keep track of the order of the columns in a board, the issue types, and allowed statuses. |
| Project updated/deleted | Detect if project name or key changed. Detect if software project should no longer be available. |
| Sprint created/updated/deleted/started/closed | Keep track of sprint status and completion rate. |
| Issue created/updated/deleted | Keep track of issue status changes, timestamps, sprint changes and other relevant details. |