How many votes does it need for this to be implemented? I'm guessing with this being open now for 4 years it's never going to happen?

Nikita, you can work around this by setting up a specific transition with a post function to set the resolution and then make the automation use that transition to resolve aged tickets.

Still a workaround so this issue should be addressed to let the rule itself set the resolution and use the standard transition.

A lack of this feature basically makes it impossible to configure the automated resolution of support requests in Jira Service Desk.
For example, closing the tickets due to no activity etc. 
Had to set up the separate queue "To Be Manually Closed" for tickets that breached the No activity timeout - to manually go over them and Resolve with the mouse 
Terrible.

I hope to solve problem in starting point, instead of complicated automation settings.
Customer Portal JSD Cloud is missing Button for Customer to push "Resolved" "Fixed" ,  "Test-OK" , "Cancelled"  , etc...   

Enabling customer portal users to edit, reopen or close requests on their own - 

provided Devinity add-on "Actions for Jira servicedesk" - not available for Cloud
https://marketplace.atlassian.com/apps/1213697/actions-for-jira-service-desk?hosting=datacenter&tab=overview

Is it relevant topic here or what ticket ?

What add-on provides configure buttons to Portal Customer in JSD Cloud ?

Still necessary. Every patch I get a bunch of "cancelled" tickets without a resolution and there's no good way to get rid of them because this hasn't been implemented yet.

Status: Cancelled

Resolution: Unresolved

+1
Would be really nice to auto-update the resolution.

We use two different workflow transitions to our closed status:

• One transition is used by the manual process and has a validator to ensure Resolution is populated
• The other transition uses a condition to hide from the manual workflow and is only used by the automated processes. I can then set the resolution status in the Post Function of this transition.

Its more than 3 years and still no hope?

Unfortunately, the workaround posted in this issue is for Jira Server, not Jira Cloud. Has anyone else come up with a better workaround?

Right now, I'm thinking of adding a status that is something like "Ready to Close" that will send a notification to me and another person, so we can go in the ticket, manually change the status and set the resolution. Not ideal, so I'm open to other ideas.

We use the Resolve status to mark tickets as Resolved.

However, due to sheer volume of tickets, we need automation to monitor issues that are in "Waiting for customers" and have no activity for X duration of time.

When that condition is met, I need AUTOMATION to set the ticket to Resolve with a specific resolution status "No Response", for example.

So having the ability to get automation to set the resolution is making our lives easier. Also, this is just one use case... there are many.

Please promote this in your queue and add the Resolution in the Edit Issue for automation.

Issue appeared for us when using "update incident when linked problem transitions". We wanted to resolve incidents when linked issue is also resolved and released. We wanted to trigger transition which moves incident to resolved status however there is not option to update resolution status in rule options and we were left with many issues with missing information. We know now about workaround but that force us to add additional artificial transition to fix resolution (using automation plugin). We would be glad to have this option presented in Service Desk automation feature for clarity sake.