SLA Goal setting

To track whether SLA is achieved or not, users can set goals. SLA Time and Report users can set 3 types of SLA Goals:

Time limit based on Single-Projects (the calculation will be based on the number of hours and minutes that Issues are expected to be moved from Start to Stop conditions)
Time limit based on Multiple-Projects (the same functionality as the usual Time limit based, but it is possible to set up SLAs for several projects at the same time)
Negotiated goals (the calculation will be based on a definite date and time set in the Issues field. (E.g: Due Date)

You can select the goal type you would like to use when you start SLA config creation. Just click the “Add new” field and choose one of the three displayed types.

The time limit based SLA type allows you to set the specific amount of time permitted to resolve the ticket. For example, 2d 6h 30m.

1 day (1d) equals 8 hours by default and can be changed in the settings of the selected Work Schedule.

You can set Custom Field for each goal type and add an Automate action for exceeded issues.

There are such Automate actions for exceeded issues:

notification
changing assignee
changing priority
changing status

The trigger time limit will be highlighted with the color you have chosen before. When the time limit is exceeded, the color will be automatically changed to red. You can monitor SLA Time for each issue with the configured multi-triggers list.

Context by Priority feature lets you assign specific priorities to service goals. This means that goals are tracked based on how important tasks are. It helps you manage and evaluate SLA performance better. This feature is only available for Time limit based SLAs.

First, create goals in the configuration:

Next, we can choose one of the priorities:

The goal will start the countdown if the priority set in the goal is the same as in the ticket.

The negotiated date SLA type is about setting SLA goals based on any issue date or time field. For example, Due Date, Updated date, etc.

Pay attention that Pause condition, First/Multi-cycle options and SLA Reset are disabled for SLA configs with negotiated date.

If you need other values, you can always create custom fields in your Jira settings.

Related use case: How to use SLA Goals as Escalations

If you need help or want to ask questions, please contact us at SaaSJet Support or via email at support@saasjet.atlassian.net

Haven't used this add-on yet, then try it now!