Automation rule went rogue

[Cristian Casanueva]

I have recently added the automation rule, which creates a new issue and transitions it to the status in progress. But instead of creating an issue, it simply moved previously existing tasks from "done" status to 'to do". The tasks that were transitioned have nothing to do with the automation rule - it should be creating a new separate issue.

Has anyone ever encountered similar bugs? Here's the flow of the automation.

[Bill Sheboy]

Hi @Cristian Casanueva -- Welcome to the Atlassian Community!

It seems you wanted to transition the newly created issue, rather than an issue from the trigger.  If so, your rule was incorrect, and the fix is to add a branch to the most recently created issue before the transition.

Automation rules are very helpful, adding missing capabilities to Jira and reducing redundant work.  However...rules can cause great harm when used incorrectly, and sometimes those changes cannot be undone.

Before using automation rules further, I recommend learning more about the structure and operation of rules.  Please refer to these documentation and example sources:

• https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

After reviewing that information, please meet with your Jira Site Admin to discuss the problems you are trying to solve and how to address them better with automation.

Kind regards,
Bill

[Sharumathy Krishnan]

Hi @Cristian Casanueva 

The automation which you have created looks good. However, it is advisable to incorporate a branch prior to the transition change. This will enable you to modify the transition exclusively for the tickets that were generated through this automation. Below is how I tried, let me know if this works for you.

Thanks,

Sharu

Empyra Software Solution