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
Has anyone found more information with regard to this? I'm running into the exact same problem described here.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Additional changes below were performed but i still get the same error:
"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):
QAERPHD-197 (Customer Action - 10399)"
1. instead of {{#changelog.status}}{{fromString}}{{/}}, i used {{#changelog.status}}{{from}}{{/}} to store the status ID in GITERP Previous Status in the first rule.
2. i tried different Field Types for "GITERP Previous Status" (Short Text, Paragraph, Number) to store the status ID.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
K believe there was an older issue with this that then required a workaround.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ismael Jimoh ,
Yes, i tried the smart value, {{fieldChange.from}}, which was mentioned in the workaround but it seems it doesn't return any value to the field "GITERP Previous Status". May i know what am i missing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.