My team uses a Jira Service Management project in Jira 8.13.
We have a single SLA set up, with goals that distinguish by calendar (Australia, NZ, or India) and priority (Minor/Trivial or a higher priority).
Occasionally an issue gets resolved without an SLA timer appearing on it.
Usually this is because the assignee got added after resolution. My team has changed their behaviour so this almost never happens any more (win!).
However, I'm still seeing a few issues that are resolved without an SLA timer. None of them have the anti-pattern I already know about (resolving before selecting an assignee). I need help identifying what's going on.
Can you help me play Spot the Difference? Or point me to problems I haven't noticed?
Here's the config of the SLA:
Here's an issue with an SLA timer (this is GOOD):
Here's an issue without an SLA timer (this is the BAD one):
I'm intrigued - are the bad / no SLA tickets coming from all of the areas, or only from New Zealand?
The first idea I can offer is that you're using the "IN" operator in a couple of your SLA rules (the ones that reference NZ time) where you only have a single value in the parentheses. I would try swapping out
in (si551399)
for
= si551399
Alternately, I don't see a field for Epic Link - Is it possible that your bad / no SLA ones have an Epic Link set that you just don't see because of the Request's field config?
Thanks very much for these 3 ideas.
I'm going to keep looking for more patterns within the problem tickets.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.