I had similar need to use an operation Bult Edit field Resolution with Jira, cause of bad workflow in business process = some post process functions wasn't added for a long time.
I think there is no ability to edit field Resolution with Bulk operations, I found this: Task for the problem
But you could do this changes one by one for every task or add some steps in workflow and send all tasks to this steps (you could change field Resolution inside steps with post process function).
The problem with a bulk edit for the resolution field is that the update date will not accurately reflect the actual resolution date. Instead it will reflect the bulk edit date.
We didn't have the Resolution field in our tickets and want to go back to update all the closed tickets with a value in that field (and the Res Date), but don't know the best approach right now. Looking for a good solution.
Take note of the temporarily in that answer - you must do this edit during a time that others are unlikely to be editing issues, and you absolutely must remove the field after you've done the bulk edit.
Otherwise people will be resolving issues incorrectly when editing them.
Ok, so "Change resolution" is not appearing anywhere in that list? I'd expect it to be a bit below "change comment" - the first batch of fields you see are "system" fields, so it usually falls in there. The second section is an alphabetically sorted list of custom fields.
The other thing we need to check is that the resolution field is on the edit screen for all of the issues being edited. If it's not available for one or more, then the bulk-edit has to drop it.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...