Transition Issue using Smart Value fails with error "Destination status could not be resolved"

Question

Hi Experts,

I have 2 rules.  First rule records the previous status in field "GITERP Previous Status" using   {{#changelog.status}}{{fromString}}{{/}}.

Second rule transitions the status from CUSTOMER ACTION to previous status using smart value   {{issue.GITERP Previous Status}}   in the Transition issue action

During testing, it doesn't automatically transition though.  Logs and comment below.

May i know your thoughts on what is wrong here?  Did i assign the incorrect smart value in the field "GITERP Previous Status"  in the first rule?  What else can i try there?  Thank you

Peter · Answer

@Bill Sheboythank you for the response.  This is a company-managed project.  Using number (in the form of {{fieldChange.from}} instead of {{fieldChange.fromString}} worked!  I had tried this previously, but it must have been before I made some other changes to the Automation, because it didn't work then but works now.

Thank you for the suggestion!

Bill Sheboy · Answer

Hi @Peter

Are you using a team-managed project or a company-managed one?

I wonder about this symptom for team-managed projects, where the status values are defined by project, and so can cause issues when the names are the same as for other projects.  (Dashboards are a good example of where that causes chaos.)

Perhaps a work-around/solution would be to ensure that the ID value for the status is explicitly used instead of the status name...Although I haven't tried that.

Best regards,
Bill

Peter · Answer

Has anyone found more information with regard to this? I'm running into the exact same problem described here.