I am trying to clone the issues without changing its status. But the Automation does not work.

[Pooja Sree]

With the help of Atlassian community, i was able to find a way to clone the issues and retain their status. I have added the automation rules perfectly (atleast i think so) but i am getting the below error messages. 

Transition Issue:

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):

TT-264 (Unassigned - 10009)

 @Ste Wright Could you please help me fix this?

[Trudy Claspill · Accepted solution]

Please show us the details of the Transition step in the rule.

In this case you appear to be trying to transition an issue that is a clone of another issue.

Are you trying to transition that issue to the same status that the original issue is currently in?

Are these issues in the same project? Are these issues the same issue type?

When an issue is cloned it will be set to the initial Status for the workflow for that type of issue in that type of project. If you are trying to set the status of the new issue to match the status of the original issue have you confirmed that you could make that transition manually in the UI to confirm that is a valid transition path?

[Pooja Sree]

@Trudy Claspill Here's the Transition step in the rule.
Yes, Transitioning issue that is a clone of another issue.
Yes, I am trying to transition the issue to the same status that the original issue is currently in.
The issues are in the same project and same issue type. Yes.
No, I have not confirmed if i could make that transition manually in the UI to confirm that is a valid transition path. Please let me know how to do this. 

[Trudy Claspill]

As @Charlie Misonne said, the way your rule is currently written, when you use "copy from issue" in that step "issue" is referencing the trigger issue, so the result is the rule is trying to change the status of the newly created issue to the status it is already in.

What you want is to change the newly created issue (the issue triggering the rule) to the Status of the original issue from which it was cloned.

I have figured out a way to get the information from the original issue, but not yet successfully figured out how to use that to transition the trigger issue.

Charlie's suggestion to branch to linked issues and execute the transition within the branch won't work. When you are within the branch the Transition Issue action will operate against the linked issue, not the trigger issue.

[Pooja Sree]

Hi @Trudy Claspill Thankyou! I have tried Transition issue to "Copy from Issue" and "Same Status (LOOP)" But unfortunately, none of it works. 

[Pooja Sree]

@Trudy Claspill Hi Trudy, Please let me know if there is any other way to retain the status of the cloned ticket, other than automation. 

Thankyou! 

[Trudy Claspill]

Hello @Pooja Sree 

I have found a different rule construct that will get you what you want.

With this rule, if an issue is created by Cloning another issue, then the new issue will be transitioned to the same status as the original issue if that is a valid transition per your workflow.

This rule is triggered by creation of the "cloners" link between two issues. That happens when you manually clone an issue. It would also be triggered if you manually create the clone link between two issues that already exist.

If you are using another rule to Clone the issue, for this new rule you will need to check the box on Rule Details that says "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

Note that the transition will work only if the status change from the new issue's current status directly to the status of the original issue is a valid transition in your workflow. 

[Charlie Misonne]

Hello!

First question: does you workflow allow status transitions to all statuses?

Secondly: your transition action will not work. You chose "copy from issue" but the "issue" in scope is the actual issue that was created. What you are doing here is copy the status from the current issue and transition it the the same status again.

Instead you should use a for each branch of type Branch rule / related issues like this:

Make sure you use the correct linked type (could also be "is cloned by").

And then you can get the status from the issue like you did:

[Pooja Sree]

@Charlie Misonne Hi Charlie, I cannot allow workflow statuses to transitions to all statuses, as the same workflow is linked to many projects/Issue types.
I have added Branch rule, but still no result.

[Bill Sheboy]

Hi @Pooja Sree 

When you want a cloned issue to have the same status as the source issue (although I am unclear of your use case for that) it usually happens immediately after the cloning.

So, where does the cloning happen:

• if you clone the issue from inside of a rule, the status can be set
• if you clone manually (i.e., from outside of a rule) you must manually set the status

Kind regards,
Bill

[Anush Chatikyan]

so how it's possible after cloning the tickets have the ticket status as new not to copy the status and make the same as the original is. 

[Bill Sheboy]

Hi @Anush Chatikyan 

As this is an older thread, I recommend creating a new question and linking back to this one.  Otherwise that limits the suggestions to only those people following this one.  Thanks!

Until then...

Please see the above post, as how the issue is cloned determines how to change the status.

Kind regards,
Bill