You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Atlassian Community!
Just posting a quick update here to let you know about a change we’re making to how automation rules are run.
All automation rules start with a trigger. These can be based on an event (e.g. When an issue moves to Done…) or they can be based on time (e.g. Every 2 weeks….).
However, some rules can be triggered manually. You can set these up by selecting the Manual trigger when creating an automation rule.
Once you’ve created a manual rule, you and your team can trigger it by going to a Jira issue and selecting Rule executions (next to Automation).
This is great for:
By default, manual automation rules can be triggered by anyone with access to issues. You can restrict who can trigger your rule, by choosing a permission group under Groups that can run trigger after you've selected the Manual trigger.
Learn more about permission groups
From March 2023, we’re moving manual automation rules to the Actions menu, which you’ll find next to Status. This menu will include both manual automation rules and looped workflow transitions (where a transition keeps an issue in the same status and performs an action).
We’re doing this for two reasons:
Thanks for reading! If you have any questions about this change, or any other feedback about Automation in Atlassian Cloud, please feel free to leave a comment.
Senior Content Designer - Automation
52 accepted answers