Manage permissions
Time to SLA lets you set granular permissions for each TTS menu based on user roles and group types. This ensures that team members have the appropriate access based on their responsibilities.
This page explains how to grant users permission to access Time to SLA menus and the purpose of each permission setting.
Jira administrators have full access to all Time to SLA features, even if they haven’t been explicitly granted permissions. This is due to their global administrative privileges in Jira.
How to manage user permissions
Navigate to Settings > Permissions in the app.
Below is a detailed explanation of the different Time to SLA menus and their respective access permissions:
Get started | Grants access to the Get started page, which provides an overview of the app’s capabilities and serves as an introduction for new users. |
SLAs page | Access to the SLAs page, where users can create, edit, and manage SLA configurations. |
Calendars | Access to the Calendars page, where you can manage working hours, business calendars, and holiday schedules used in SLA calculations. |
SLA panel | Ability to see the SLA panel on the Jira work items. |
SLA History tab | Grants access to the SLA History tab within Jira issues, which records SLA start and stop events, breaches, and recalculations. |
Customer portal SLAs | Access to the Space settings > Apps > Time to SLA customer portal settings, where you can set the visibility of the SLAs on your Jira Service Management portal. |
Permissions | Access to the Permissions page, where you can configure who has access to different menus and features in Time to SLA. |
Recalculation | Access to the Recalculation page, where you can run SLA recalculations for work items when necessary. |
Settings | Access to the Settings > General, Advanced, SLA Calculation Scope, and Notification Template screens. |
SLA panel settings | To be able to view Settings > SLA panel page, you must also have SLA panel permissions. |
Reports | Access to the Reports page, where you can generate reports. |
Audit logs | Access to the Settings > Audit logs page, where you can track changes made to SLA configurations, permissions, and other settings. |
API token | Access to the Settings > API token page, where you can create tokens for REST calls. |
Import/Export | Access to the Settings > Export/Import screen, where you can export or import SLAs and calendars. |
SLA work item operations - Reset SLA | Access to the Reset SLA operation in the TTS Issue actions tab. |
SLA work item operations - Undo reset SLA | Access to the Undo Reset SLA operation in the TTS Issue actions tab. |
SLA work item operations - Where is my SLA? | Access to the Where Is My SLA? operation in the TTS Issue actions tab. |
SLA work item operations - Recalculate SLA | Access to the Recalculate SLA operation in the TTS Issue actions tab. |
SLA work items operations - Mute SLA notifications | Access to the Mute SLA operation in the TTS Issue actions tab. |
Click Edit to change the permission settings.
Add singular or multiple groups and/or users to grant permission.
Click Save.
Check out this cheatsheet to learn more about some types of Jira groups and what they mean:
Group name | Definition |
|---|---|
jira-admins | A Jira administrator is a user with the Administer Jira global permission. |
jira-servicemanagement-users | Users in your service space are people who work on or send requests. |
site-admins | Site admins administer the users and groups for the site's products. |
system-administrators | Those with the Jira System Administrator permission can perform all administration functions in Jira, while those with only the Jira Administrator permission cannot perform functions that could affect the app environment or network. |
For further information, refer to Atlassian’s documentation.
Are you getting a 403 error even though you have the necessary TTS permissions? This can be because your Jira Cloud instance doesn't have the necessary permissions. SLA is a third-party app, and it needs some Jira permissions to work properly. To fix this, make sure you have atlassian-addons-admin added in the global permissions.