Automation issue: Close resolved issue not working
Asked by Mkrtich Tono:

I have created this automation and double checked couple of times, I want to close solved tickets automatically but for some reason the automation is not triggering even its not running by force run.   

In bellow screenshot as you can see there are more than 800 tickets needs to honor the trigger but the transaction is not happening and in the logs its listed as: No Actions performed.   

I changed the actor and made it my self still same issue.   

<br />

<br />

<br />

![1.png](/t5/image/serverpage/image-id/299292i775246CD20F31C19/image-size/large?v=v2&px=999 "1.png")![Screenshot 2024-01-08 113741.png](/t5/image/serverpage/image-id/299294iBD5CAF240616AD26/image-size/large?v=v2&px=999 "Screenshot 2024-01-08 113741.png")![Screenshot 2024-01-08 113800.png](/t5/image/serverpage/image-id/299293iCCFC7AB045D85435/image-size/large?v=v2&px=999 "Screenshot 2024-01-08 113800.png")


Answers:
author: Mkrtich Tono
body: [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) thank you for your reply, I have untick the option and tried to run the automation, now I can see that there are some errors in the trigger, with the following error code:  
*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): (then the list of the tickets)
<br />
![Screenshot 2024-01-08 125141.png](https://community.atlassian.com/t5/image/serverpage/image-id/299306iE6A64B10BBC602D2/image-size/large?v=v2&px=999 "Screenshot 2024-01-08 125141.png")*

Your advice will be greatly appreciated  

comments: author: Marc - Devoteam
body: Hi [@Mkrtich Tono](/t5/user/viewprofilepage/user-id/5351215)

This is due to the fact you use the "$" sign, this is a reserved keyword.

Due to the status name with a "$" , automation sees this as smart value, rename you status to "Closed".

This should fix your problem.


author: Mkrtich Tono
body: Hello [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976)

I have changed the status from workflow and removed the $ sign, but still have the same issue ![Screenshot 2024-01-08 153833.png](https://community.atlassian.com/t5/image/serverpage/image-id/299331iA61205FB1EC72A54/image-size/large?v=v2&px=999 "Screenshot 2024-01-08 153833.png")![Screenshot 2024-01-08 154010.png](https://community.atlassian.com/t5/image/serverpage/image-id/299330i6F2F3A3AADC20983/image-size/large?v=v2&px=999 "Screenshot 2024-01-08 154010.png")


author: Marc - Devoteam
body: HI [@Mkrtich Tono](/t5/user/viewprofilepage/user-id/5351215)

2 options:

1. The simplest solution is to change the Actor in the Automation Rule into your user or any user who has permission to apply this transition, also the permission to close an issue.
2. Maybe you need to use 10160 status ID (numeric status ID) in your smart-value for automation rule (if using smart values)


author: Mkrtich Tono
body: [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) thank you but I have tried the both options and they did not worked :(((


author: Marc - Devoteam
body: Did you remove the $ sing in your JQL on the scheduled trigger as well.

Why are you using $ sings as I don't seem to see then in you workflow.

Can you show the full automation with details on each step and your workflow?  

This is standard why to close issues, so it should have to do something with the rule, workflow (conditions, validators, status names) or permissions.


author: Mkrtich Tono
body: [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) thank you for your reply!   
I have removed the $ sign from a couple of places and changed the actor to me again and it worked thank you!


author: Marc - Devoteam
body: Hi [@Mkrtich Tono](/t5/user/viewprofilepage/user-id/5351215)

I see the trigger of the automation there is a tickbox saying "Only include issues that have changed since the last time this rule executed".

Can you try to untick that and run the automation once more.

If the rule runs, change it back after the succesfull run.


Tags: cloud

jira-service-management

jira-service-management-cloud