Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

automation have some errors

Kamil Askerov April 16, 2024

Salam. My automation have some errors. Please help me to solve this problem. 

 

--Action details:

--["10060","10053"]
--Issue condition
--The following issues passed:
--951
--Issue condition
--The following issues passed:
--62
--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):
--62 (To Do - 10027)
--Comment on issue
--Comment added to issue
--Dev Transition: Issue Transitioned to {{triggerissue.status.name}} by
--{{initiator.displayName}}

Comment is added but status not changed. I have many automations like this one but havent same problems in other automation.

Looks like error is because use not utf8 letters. "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)" How to resolve this problem? 

automation is 

aut1604.png

1 answer

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 16, 2024

Hi @Kamil Askerov,

The error occurs when the rule tries to transition an issues to a status that is not available for that issue.

Your rule wants to execute the  same transition your trigger issue went through - for all issues linked to that issue. If there is an issue in a different status or an issue in a different project (especially if you are using team managed projects), it is very well possible that this specific target status is not available for that specific issue.

Have a close look at the failed issue, check its current status and available outgoing transitions and make sure that the same transition as the one your trigger issue went through is available there. That will, most likely, not be the case.

Hope this helps!

Kamil Askerov April 16, 2024

@Walter Buggenhout  hi. You are right. I found that 1 status is different. status open in 1 project and new in other project. But I cant change that statuses. 

 

There write this message

A status with that name already exists, please enter a different name.

in workflow when i trying to change status from open to new. How I can change that status?

Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 16, 2024

That depends if the workflow this status is in is company managed or team managed.

If it is company managed, you will most likely need to create a copy of the existing workflow and then, editing that copy (assuming you want to replace open with new):

  • Add the existing New status to the workflow
  • Make sure the New status gets the exact same transitions as the Open status
  • Connect the Create transition that is most likely going to the open status to New
  • Remove the Open status from the workflow

After that, you will need to edit the workflow scheme that is now using the old workflow with the open status in it and replace it with the new version you just modified.

After that, publish the updated workflow scheme. It will ask you to review the status mapping. Make sure to map the old open status to new.

Or, probably easier: you might also connect the workflow scheme that your other projects are using with the one project that has the different workflow.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events