In simple terms
I am not sure whether I got your question right as Jobin already said reopening is needed anyway. Anyway my answer as per what I read from your description:
You can add an additional workflow transisiton (destination step as the Closed itself) in your workflow to clear off the editable flag for the issue. Once done you can do a bulk edit and also select not to notify the users while editing.
I am loathe to dredge up an old thread, but this is still the most accurate advice, albeit with a quick update:
In my OnDemand JIRA configuration, I am unable to edit any of the time tracking fields as part of a bulk change. I had to add a transition post function to set the remaining estimate to 0 on close, and then bulk close the issues. This was what I wanted to do in the first place, so it worked out well, but this may trip other users up so I wanted to specify.
The transition post functions are available when editing a workflow by clicking on the resulting status. There will be "Conditions", "Validators", and "Post Functions". Click "Post Functions", click "Add Post Function", scroll to the bottom and select "Update Issue Field", click "Add", then select "Remaining Estimate", and enter "0m" for the remaining estimate. Now, when you perform the bulk change, the remaining estimate will be set to 0, and this will happen for all future issues being closed this way as well.
As per JRA-5034, it's currently not supported to set the remaining estimate via Bulk Change.
So it's either setting one by one or write a script for that...
For the future, you can set up your workflow to modify Remaining Estimate to 0 when the issue is transitioned to Resolved/Closed status.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG