Settings

Settings

Time to SLA offers default settings for optimal use and performance. On the Settings page, you can modify and adjust some of the default values to suit your needs and system.

image-20251021-204141.png
  1. General: From this section, you can select a time zone for the 24/7 calendar, which allows the app to make calculations based on that specified time zone.

  2. Permissions: Manage access permissions to control who can interact with Time to SLA. Refer to this page for details.

  3. SLA Panel: Here you can customize your SLA panel settings, such as where the panel appears and what’s shown on the screen. Refer to this page for details.

  4. SLA Calculation Scope: On this page, you can define a Whitelist (a list of work item types to include in SLA calculations) and a Blacklist (a list of work item types to exclude from SLA calculations). Refer to this page to learn more.

  5. Notification Template: Here you can configure the appearance of the default email and Slack notifications. This will ensure you don’t have to change the default template in the SLA Notification for each notification every time. Refer to this page to see the available notification parameters.

  6. Import/Export: This page provides options for efficiently transferring data in and out of the Time to SLA for Jira Cloud app. For more details, refer to this page.

  7. API Token: This is where you generate and manage Rest API tokens, which can help you edit and view your SLA data. For more information, refer to the documentation.

  8. Audit Logs: Stay informed about the actions taken within your Time to SLA environment by accessing detailed audit logs. Refer to this page for more details.

  9. Advanced: In this section, you can specify how frequently you’d like the SLA Target Date custom field to update the Target Date on an SLA and how often reports and audit logs should be deleted. There is also an option to:

    • Exclude automated users – Prevent automated accounts from triggering Time to SLA. You can use this to exclude events from service accounts, bots, and other automated users that don’t require SLA calculations.