Transition to Up Next if certain text is in the Summary

[deseymour]

I am trying to set up automation that only moves a task to Up Next if there is certain text in the Summary field of the task. I've attached a screenshot showing how I set this up, but it seems to just run this on every task that is created instead of only on the ones that have the correct text in Summary. I may be wrong about that...my log shows No Actions Performed for all that do not have that text...so does it actually just run the automation to see if that text is there and if not, it just lists No Actions Performed? If so, am I charged for those runs against my automation limit?

[Arkadiusz Wroblewski · Accepted solution]

Hello @deseymour

Your understanding is exactly right. The rule will trigger for every new issue, but if the summary doesn't match your text, the condition stops the flow immediately, resulting in a "No Actions Performed" log.

The good news is that runs terminating at a condition without executing an action do not count against your monthly automation usage quota.💪

For the setup itself, stick to a basic Issue fields condition (Summary > contains > your text) rather than advanced JQL, as it is much easier to maintain. Just double-check that the transition to "Up Next" is a valid path from the issue's initial creation status, or the rule will fail at the final step.

Best,
Arkadiusz🤠☀️

[Bill Sheboy]

Hi @deseymour 

Please look here to learn what does (and does not) count as usage for automation rule, monthly limits and service limits

• https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/
• https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

And as a reminder based upon the rule you show...

The Work Item Created trigger has known racetrack timing defects.  Thus, the rule can start processing before all of the data is available, leading to errors and unexpected results.  The mitigations for this defect (until Atlassian fixes it) are:

• Always add the Re-fetch Work Item Data action immediately after this trigger.  This will slow the rule slightly, reloading the data before the steps proceed
• Never use the new feature adding conditions directly to triggers.  Because the data may be incomplete, the conditions results will be unpredictable.  Instead, add separate conditions after the above noted re-fetch action.

Kind regards,
Bill

[Thiago Wenceslau -Appfire-]

Hi @deseymour 

I’m Thiago, a support engineer at Appfire.

If you are considering third-party apps, you could change the default workflow of the issue with a Post-Function using JMWE(Jira Misc Workflow Extensions), here’s how:

First, I assume you already created the “Up Next” status, if not, please create, save your workflow and wait a couple minutes for the JMWE app index the changes.

Reopen the edit workflow page, click the “Create” transition and add a new rule, this rule will be the Transition Issue(JMWE app). I'll leave an example image below, make sure you select your workflow scheme and the "Up Next" status in the Transition Picker button. 



Using this rule, we can transition the issue after it has been created if it matches the summary validated by the Nunjucks conditional validator. Remember to check the delayed execution box at the end and make sure the rule is below all the actions in the Create action:



Regarding Automation Limits: Since JMWE runs directly within the Jira workflow engine, transitions triggered by our post-functions do not consume your Jira Global Automation limits/tokens.

Please contact our support if you have any other questions about this.

Best regards, Appfire support team.