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!


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
Community Members
Community Events
Community Groups

Atlympic Event #Atlympic | Automation

I'm a huge fan of Jira automation rules!


A few of the ones I've created in my current company for my team.

1) Assigning tickets in a specific column to a specific person

Screenshot 2021-07-27 at 10.42.08.png

2) When a ticket is blocked by another ticket, add a flag

Screenshot 2021-07-27 at 10.42.32.png


3) When a new ticket is created, send an email to the Product Owner with more info

Screenshot 2021-07-27 at 10.45.12.png

4) When a linked story is cancelled, remove the link

Screenshot 2021-07-27 at 10.43.22.png

5) When a new story is added in the middle of the sprint, inform the whole team via Slack about it

Screenshot 2021-07-27 at 10.43.44.png


looks good

Thanks @Anita Kalmane  for sharing.

Taranjeet Singh Community Leader Jul 27, 2021

@Anita Kalmane Great work with automation for your team!

Hi @Anita Kalmane 

Thanks for the information! 

As you seem to be using Scrum, please take care when using your rule 1) Assigning tickets in a specific column to a specific person.  For teams using agile methods and pull-based work, pushing work onto someone who doesn't have capacity could overwhelm them...and stall the work waiting for them to start it, or ask for help.

Perhaps chat with the team if this is a concern, particularly when the rule detects the {{initiator}} (person who did the transition) is not the same as the person the rule is about to assign the work to.

Best regards,

Like Anita Kalmane likes this

Thanks for the feedback, @Bill Sheboy ! In this case, the reason for adding the rule was to make sure the PO doesn't forget to look at the ticket on the same day when they're ready for approval. There is no question of too much work, simply the PO doesn't check the board so often as the rest of the team, hence this way we help them to remember. Otherwise totally agree with your comment, we don't want to overwhelm people or have only some dev team members specialised in certain tasks.

Like Bill Sheboy likes this


Log in or Sign up to comment