Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Button handy
blankfalse
color#0052CC
nameCloud
linkhttps://appfire.atlassian.net/wiki/spaces/TTSC/pages/48529969/Defining+an+SLA+Calculation+Scope
width84
Button handy
blankfalse
color#EBECF0
nameOn-Prem
linkhttps://appfire.atlassian.net/wiki/spaces/TTS/pages/48334013/Defining+an+SLA+Calculation+Scope
width85

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#F4F5F7

This page is about Time to SLA for Jira Cloud. Using Jira On-Prem Data Center? Click the On-Prem button abovehere.

The Time to SLA add-on listens to all issue events and recalculates SLAs at each issue event, providing consistency across all issues for all SLAs. However, some ensures consistency across all SLAs by recalculating them for every issue event. However, not all projects or issue types may never require SLAs, so it may be a good idea to . Instead of filtering them out using JQL in each SLA definition, you can completely exclude these projects or issue types from the SLA calculation rather than eliminate them with JQL in each SLA definition.Time to SLA allows you to define a Whitelist (a list of SLA calculations.

To refine the scope of your SLA calculations, Time to SLA offers two filtering options:

  • Whitelist: Includes only the specified projects and issue types

...

  • in SLA calculations

...

  • .

  • Blacklist: Excludes the specified projects and issue types

...

  • from SLA calculations

...

  • .

...

For example, examine the screenshot below:

...

In this case, only the projects (Appfire Service Desk) and issues in the given scope (Task and Subtask) will trigger the SLA calculation. You won’t see the SLA Panel on other projects or issue types. This means that once you define Whitelist rules, any issue that does not fit into those rules will be excluded from the SLA calculation.

...

These filters allow you to tailor SLA calculations to the specific needs of your organization.

On this page:

Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printabletrue

How it works

Whitelist

When you define a Whitelist, only the specified projects and issue types will trigger SLA calculations. Issues that do not match these rules will be excluded, and the SLA Panel will not appear for them.

Info

Example:

If the Whitelist includes the project Appfire Service Desk and the issue types Task and Subtask, SLA calculations will occur only for those issues. The SLA panel will not appear in other projects or for other issue types.

Screenshot 2025-01-27 at 18.30.27.pngImage Added

Blacklist

When you define a Blacklist, the SLAs will apply to all projects and issue types except those specified in the Blacklist rules.

Info

Example:

  • If the Blacklist specifies the project B-Team, SLAs will be excluded from this project.

    Screenshot 2025-01-27 at 18.30.58.pngImage Added
  • You can also define Issue Types, which would mean your SLAs will appear on every issue except those you've defined in the project

...

Note
  • .

Combining Whitelist and Blacklist

If both Whitelist and Blacklist rules are applied, Blacklist rules take precedence over Whitelist rules.

If you use Whitelist and Blacklist rules together, blacklist rules will precede whitelist rules

...

Here is a brief how-to:

...

Go to Jira Cloud > Apps > Time to SLA.

...

Open Settings > SLA Calculation Scope.

...

Select Projects and/or Issue Types for Whitelist and/or Blacklist.

...

.