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
Next: Root
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.
I already have an automation rule set up in my Jira Service Management project using the JSM automation. Now I would like to add another rule and it seems the Project automation is easier to user for this particular case. Can they both be used on the same project? Does it have to be on different events or do they each have their own event processor?
Welp, considering that Atlassian has decided to start turning off Legacy automation (that's what your first rule was setup in), it might be good to switch over to the newer automation engine.
https://support.atlassian.com/jira-service-management-cloud/docs/what-is-legacy-automation/
But in answer to your questions:
1. Yes you can use both automation engines with the same project. And in fact, the Legacy automation is the only way to still do certain actions (like changing a JSM request type). Hopefully they fix that one before killing Legacy automation (currently scheduled to begin rollout on Aug 30, 2021.)
2. And yes, you can have rules from each be triggered by the same events. I don't know which one takes precedence though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.