Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Jira Service Desk Automation

I'm looking to setup a customized automation rule in Jira service desk, below is the criteria:

Triggered: when an issue is created 

If: Work-effort type = "yes'

Then: Update Priority to 'High' 

I have created this rule and applied it but when a request comes in and meets the above criteria, the priority doesn't change to 'high'. When I check the rule's log, it does show the specific issues meeting the criteria. Additionally I am the project owner so permissions shouldn't be an issue. Any thoughts on why this may not be working properly? 

1 answer

0 votes
Bill Sheboy
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.
Apr 15, 2021

Hi @Derek Guzenski  -- Welcome to the Atlassian Community!

Would you please post images of your automation rule and an audit log entry showing a case where you expected the value to change?  That will provide more context for the commuunity to offer ideas.  Thanks!

Best regards,


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events