SLA Goal setting

Owned by Stepan Fedortsiv_SaaSJet
Last updated: Oct 19, 2023 by Kateryna_v_SaaSJet_ (Deactivated)
3 min read

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

  • Time limit based (the calculation will be based on the number of hours and minutes the Issues are expected to be moved from Start to Stop conditions)

  • 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 two 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.

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.

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.