automation have some errors
Asked by Kamil Askerov:

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

--Action details: {#toc-hId--379288594}
---------------------------------------

--\["10060","10053"\]  

##### [--Issue condition](https://sinam.atlassian.net/jira/settings/automation#/rule/18697041/429028063) {#toc-hId-1012337458}

--The following issues passed:  
--951  

##### [--Issue condition](https://sinam.atlassian.net/jira/settings/automation#/rule/18697041/429028065) {#toc-hId--795117005}

--The following issues passed:  
--62  

##### [--Transition issue](https://sinam.atlassian.net/jira/settings/automation#/rule/18697041/429028066) {#toc-hId-1692395828}

--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](https://sinam.atlassian.net/jira/settings/automation#/rule/18697041/429028067) {#toc-hId--115058635}

--Comment added to issue  
--Dev Transition: Issue Transitioned to {{triggerissue.status.name}} by  
--{{initiator.displayName}}  

--Associated items: {#toc-hId--826626317}
-----------------------------------------

##### [--Issue event](https://sinam.atlassian.net/jira/settings/automation#/rule/18697041/429028062) {#toc-hId-564999735}

* [-951](https://sinam.atlassian.net/browse/NASESDA-951)  

##### [--Branch rule / related issues](https://sinam.atlassian.net/jira/settings/automation#/rule/18697041/429028064) {#toc-hId--1242454728}

* [--62](https://sinam.atlassian.net/browse/SRNASESDA-62)

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](https://community.atlassian.com/t5/image/serverpage/image-id/318587iAB8ADA6F4511D381/image-size/large?v=v2&px=999 "aut1604.png")


Answers:
author: Walter Buggenhout
body: Hi [@Kamil Askerov](/t5/user/viewprofilepage/user-id/5450722),

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!

comments: author: Kamil Askerov
body: [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) 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?


author: Walter Buggenhout
body: 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.


Tags: cloud

jira-service-management

jira-service-management-cloud