Transition issue. Destination status could not be resolved

[riccardo.pedrinelli]

Hi folks,

i have 2 project, let's call it Origin and Clone, when a ticket is opened on Origin i manually clone and move the issue to Clone.

I set up an automation on Clone that align the status of Clone ticket on Origin one, but i got :

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)

The rule have the permission to work on the 2 projects and they have the same workflow for the issues.

Any idea?

[Anthony Morais]

Hi @riccardo.pedrinelli 

Welcome to the Atlassian Community!!!

Although the workflows are the same, check if there is a transition to the desired status, if not, create a transition and test again.

Ex: In the workflow below, the Pending status does not transition to Completed.

 

I hope it helps!

Regards,

Anthony

[riccardo.pedrinelli]

Hi @Anthony Morais ,

thanks for the suggestion. As you can see in the following images, it seems to be the same flow, but maybe you're able to notice something unlike me.

[riccardo.pedrinelli]

Seems the problem was about the fact that the origin issue had customs field not present on the cloned one.

I change the Story settings and now it works, this is a little bit strict, is it possible to avoid this kind of problem?

[Jehan Bhathena]

Hi @riccardo.pedrinelli ,

If both the issue types belong to the same project then perhaps clubbing them under the same Workflow, Screen Scheme and Field Configurations would help.

Same would apply they falls under 2 different company-manged projects.