Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,986
Community Members
 
Community Events
184
Community Groups

Time to Assign SLA is not working on cloned or Auto-created subtasks

Hi. I've established a simple SLA that starts when a Service Desk ticket is created and stops when we designate an Assignee to the Request based on Assignee: Changed condition. It works fine in this setup.

The problem occurs when someone clones a ticket and the Assignee field is already populated, so the Assignee field doesn't change per se. I also create automated sub-tasks which grabs a username from another field in the form and populates the Assignee field with it. 

Ideally, I'd like to base the SLA simply around the Assignee field not being empty but this condition doesn't appear in the SLA criteria to select. I have Project Admin only, not system. Is there a way to do this in JQL? 

Time in Unassigned SLA.jpg

 

3 answers

0 votes
Olga Videc
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 26, 2021

Hello @Richard Imbrogno 

Yes you can add JQL to SLA, under goals just add a new rule

What this does is start SLA only if Assigne is unassigned.

All remaining issues no target means, that SLA won't be set/start on those issues.

Assigne.PNG

BR, Olga

0 votes
Gökçe Gürsel {Appfire}
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Mar 07, 2021

Hi @Richard Imbrogno ,

Do you use Server/ DC or Cloud?

Hi Gokce. We use Server/DC here. Thank you

0 votes
Liam Green
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 04, 2021

Hi @Richard Imbrogno 

Does adding the option "Assignee: From Unassigned" to the Stop criteria do anything? 

Thanks Liam. It didn't unfortunately. I think because there's no real 'change' in the field this is the challenge as the change happens instantaneously.

Just thought about something that will fix this in the interim. I will add an additional label on the automated subtasks and I'll exclude that label  from the SLA counter. 

As for the manual cloning of tickets it's one team member whose tickets are auto-assigned anyways so the SLA trigger is not needed for his tickets to begin with. 

I think I have my workaround but would be good if there's a system-based solution that addresses this.

Like Liam Green likes this
Liam Green
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 04, 2021

Sounds like the workarounds are a good interim, which is great.

We have similar challenges in our own instance, so hopefully Atlassian will beef up SLAs in the future

Just an update. This work around is good with the auto-subtask creation but does not work with the cloned tickets at this point. For those who are using the Clone process I've asked them to manually add the same label as above to those specific requests and that has allowed me to bypass the SLA as a result. Kind of a hack-job but it'll work for now :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events