How to transition newly created issue cloned via automation to a different workflow status

[Nikki Colletti]

I have a manual trigger that I created that allows my team to clone an issue into another project and set some of the values on the newly created issue and to update some fields on the trigger issue once the cloned issue is created.  When creating the cloned issue in the other project it is setting the "status" to default workflow status for that project, which is not what I want.  I have a status in that project called "reporter review" that I want to transition this newly cloned item into but I am just having some trouble figuring out how to do that.  I was considering adding a tag on the newly cloned issue and then creating an automation rule in the other project to transition it, but there has to be a better way without having to run two separate rules.  Any ideas?    

[Trudy Claspill]

Hello @Nikki Colletti 

It is possible to execute the transition of the issue within the same rule using a branch and a Transition Issue action, as mentioned by @Bill Sheboy . However, since you are cloning the issue into a different project, the rule would have to be a Multiple-Project Scoped rule. Such rules can be created/modified only by Jira Product Admins from the Global Automation page under the Settings > System option.

If you are not a Jira Product Administrator you would need to get help from such a person to modify the rule to make it a multiple project scoped rule.

[Bill Sheboy]

Hi @Nikki Colletti 

After your rule clones the issue, you could branch to it to transition it.

Another option is to call the REST API endpoint to create the issue and set the status at the same time, although that would make copying the issue fields (for cloning) much more complicated.

If this does not help, please post images of your complete rule and the audit log details for context.

Kind regards,
Bill