Hi all,
I want to create an automation where if the status in one issue (lets call issue a) is changed it duplicates another pre-existing issue (issue b) and links it to issue a.
I have tried to use automation where the When: Status changed to DD/Closing and if the Property Type (a field I have created in the issue whose change triggers the action) is set to Real Estate that the ACTION will be THEN Clone issue to the same project that the triggering event happened in, the Issue Type is EPIC but I am not sure what I need to put in the Summary field to direct the automation as to what issue needs to be cloned. As per ChatGPT I have populated the summary with CLONE - {{issue.summary}} - Clone of JHP-35 with JHP-35 being the EPIC that is already set up and populated that I want cloning.
However, when I run the automation it does not work and it says that the issue condition - The following issues did not match the condition JHP - 33 (the issue that should trigger the action). But JHP 33 does meet the conditions set in the automation criteria.
Any help would be greatly appreciated, I get the feeling that this may be wrong automation as the Clone Action issue states 'This action will create a new issues and copy all field data possible. Clone current issue into', My concern here is the phrase clone current issue which leads me to believe it is trying to clone the issue that triggered the action which is not what I want, although as nothing is being created there are obviously additional issues.
Any pointers or links to where I can find this information (I find the Jira library very difficult to navigate when looking for specific actions) would be greatly appreciated.
Thanks,
Paul
Hello @Paul O_Shea
Welcome to the Atlassian community.
Can you provide a screen image of your complete rule, just so we are absolutely clear on the structure?
When you execute the same process manually, how do you know the specific "issue b" that you want to clone?
In order to clone an issue, you have to "retrieve" that issue as part of the automation rule. There is no way to plug in an issue key in the Clone Issue action.
One way you can retrieve "issue b" is to use a Branch - For Each / Related Issue / JQL. Then create a JQL statement that will return "issue b". You can then add a Clone action within that branch to clone "issue b" and link it to the trigger issue.
Your rule might look something like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.