Atlympic Event #Atlympic | Automation

[Anita Kalmane]

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

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

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

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

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

[Alexander Pappert]

looks good

[Suvradip Paul]

Thanks @Anita Kalmane  for sharing.

[Taranjeet Singh]

@Anita Kalmane Great work with automation for your team!

[Bill Sheboy]

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,
Bill

[Anita Kalmane]

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.