We currently have two separate SLAs for tickets:
Each SLA follows its own workflow for starting and pausing, but both are visible on all tickets, which is causing confusion for the Service Desk team when handling them.
Is there a way to hide the autogenerated SLA from JIRA service request tickets and vice versa to avoid this overlap?
Hi! Thanks for your reply!
I currently see this in the SLA settings (screenshot), and for the JIRA ones, no JQL has been added.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
and what JQLs are in Time to first response and time to resolution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
so for Time to resolution and Time to first response I suggest to exclude auto genetated tickets by adding issuetype != "Auto generated"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! So, it kinda worked :D
I added for the JIRA SLAs the JQL and it hid the JIRA SLA from the Autogenerated tickets (screenshot 1)
But now I don't have any SLA visible for the not-autogenerated tickets, the non-autogenerated tickets type is "Service Request"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Aire Vaigu
Welcome to the community.
Remove the autogenerated SLA if you don't require it or change the JQL in the Goal of the autogenerated SLA or the priorities that are set.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.