There are a couple of things you need to think about here.
First, the closed status often has the "do not allow edit" flag set on it. That means you can't just click "edit" and change things, and you can't use bullk-edit to change things.
Secondly, the resolution field is an odd one which is not on the edit screen and should never be added to it
So, the hard way to do this would be to get all your users to stop using JIRA, enable edit by hacking the workflow, add the resolution field to the screen, use bulk-edit to change the issues, then remove the resolution field from the edit screen and then undo the workflow hack.
A safer option is to add a an "edit resolution" workflow transition from closed to closed (maybe with a condition of "only admins") and make that go through a new "edit resolution" screen, or even just set the resolution in a post-function.
My "solution" is a little late and I'm not very experienced either.
i'm in the process of getting involved with jira and have freedom to do anything. i started with a test ticket via an email that i own to follow my steps.
i removed the "editor", "author" and "observer". then opened the ticket again to close it again with the "solution", then added the remote participants again. so i can be sure that the customers and staff don't get any mails about the change of the ticket.
it's not a nice solution, but one that works.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events