SLA configuration step by step depend of type and bug

[claudio campana]

Hi 

I would like to know how i can get the way of the configuration of the SLA depend of type bug and priority.

thanks 

[Alina Kurinna _SaaSJet_]

Hi @claudio campana 

If you want to track SLA goals based on bug type and priority, our app SLA Time and Report for Jira can help you do that easily.

With this app, you can:

1. Define multiple time-based goals
2. Set up different start/stop conditions (e.g. from status “To Do” to “Done”)
3. Apply SLA timers only to specific issue types (like Bug)
4. Add goals based on priority, severity, or any custom field
5. Trigger actions (like notifying the assignee or changing priority) when an SLA is exceeded

Here’s how it looks in the app when configured by Bug type + Priority:

You can also check out this step-by-step article written by my colleague, it shows how to monitor bug resolution SLAs effectively: A simple way to monitor bug resolutions in Jira with SLAs

If you have any questions, write or book a 1:1 demo with our product manager.

Regards!

[Christopher Yen]

Hi @claudio campana 

Please reference this article Write JQL queries for SLAs 

Below is an example of how resolutions SLAs are set for incidents in my Service Desk, using the incident work item type and our custom priority field you can use for reference. If you're using the out of the box priority field you can select them when editing the goals using the UI, but we set up our priority prior to priority contexts so we're still using a custom field. 

Hopefully this helps!

[claudio campana]

Thanks @Christopher Yen