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
I modified a rule that is triggered when an issue is transitioned to done in Service Management Cloud. It then has a related issues condition checking that linked issues of the trigger do not match a JQL querery in a Jira Cloud Project. If none match an issue is then created in that Jira Cloud Project. I have the scope set as a single project for the Service Management Project. The creator of the rule had the scope set as multiple projects with the Service Managment and the Jira Cloud Project entered in the projects field. This caused us to reach 90% of our limit. In the audit log it says multiple projects after I modified the scope so it could only be triggered in the Service Management project. It is of my understanding that cross product issue creation is treated as a single project execution.
You need to change the scope from "Global" to single project. Right now even though all of your components are restricted to a single project, the rule can will run each time any issue is transitioned to "Done".
Edit: I misunderstood the screenshots. Yes, even if the rule can only be triggered by the JSM projects, creating a new ticket in a different project makes it a multi project automation rule.