With Atlassian restricting Standard Plan JSD and JS customers from executing more than 500 Automation Rule executions per project per month, rules which execute but do not carryout an action chews up the monthly allowance and therefore renders a large portion of the highly valuable functionality of the Automation rule feature from being useful.
We have an SD project which clones issues to a Software project when they're escalated to the development team for investigation.
Our need for Automation Rules in this scenario is for comments added to the the SD project issue, to be also added to the linked issue in the Software project and visa-versa.
The rule we have created is "run when a comment is added to an issue" and has an If Block of "Linked issues present Types: All link types".
The If block was added as we're finding the majority of the comments on issues in the Service Desk project are on issues that do not have linked issues and therefore, correctly do not carryout the action of the rule.
However, as the rule has been considered as executed due to the trigger being invoked by the addition of a comment, our usage allowance is decremented even though no action has been executed.
Is there a different approach we can take to achieve the desired outcome without compromising our monthly ARU allowance?
Ideally, the ARU allowance is increased considerably or executions are only counted if an action has actually occurred. Maybe a combination of both might be more reasonable.
What we want to avoid is the need for a Jira Software user to have access to Jira Service Desk as it's much more efficient for the Jira software user to remain focused and manage their workload from within their Software project.
