Problem bulk edit field - Resolution

[Jeanne ROBERT]

Hi ! 

After looking for a long time without finding an answer, I come to ask the question, hoping to have a solution haha. I want to change the status of the "resolution" field on a lot of tasks, so with Bulk operation. At the Step 3 of 4 : Operation Details, there are a lot of fields, but there isn't "Resolution" field.

This is a short video to show it : https://www.loom.com/share/619bc5dc440f452a9eac7c3d7d56c6e3 

I don't know how to display this resolution field.... do you know how can i change that ?

Thank you for your help !

[Jack Brickey · Accepted solution]

You need to use Transition for changing the resolution not the Edit method. Depending on your exact goals this may include editing your current workflow, editing the transition within that workflow and including a post function to change the resolution field. Moreover, if this is a temporary cleanup exercise it may require you to add a temporary transition that you could use for this bulk transition operation. You might also consider looking at automation to see if it could achieve the goals you seek.

[Jeanne ROBERT]

Hi thanks for your reply ! Actually today I changed the current workflow and the transition, so now I don't have a problem with the Resolution field anymore.

But for all old tasks, the Resolution field is not up to date, so I wanted to change all old tasks in bulk from "unresolved" to "done". I will try to update it with import csv

Thank you

[Jack Brickey]

yep. common problem and you will find many posts in the Community on this.

as I mentioned above to correct do this...

1. edit the workflow
2. add a temporary transition from your done status back to itself called "fix-res"
3. add a post function to set the resolution on this new transition as desired
4. publish the workflow
5. go to advanced search and find your issues
6. use bulk edit and choose Transition
7. select the "fix-res" transition
8. verify the resolutions are as desired
9. go back and edit the WF and remove the temp transition and publish

[Jeanne ROBERT]

Hi again, thanks now it's ok for me ! thank you for the tuto haha :) 

[Marni Rader]

So is this fix a ONE BY ONE fix?

I have 166 issues to fix.

If it's one by one I can just do that in each issue.

Sorry, I don't really understand your steps.

Thanks!

[Jack Brickey]

hi Marni, the steps I have outlined include a bulk update. Once you add this special transition you can use it with the bulk edit feature. You certainly could do it one by one if you wanted.

[Jennifer DiLapi]

Hi Jack, 

Can you help me know how to create a transition from my Done status back to itself in an active workflow? 

[PhilSpo]

Just to add onto Jack's answer. If this is a temporary cleanup, then you can export all the issues in question out of jira as a .csv

Make sure you include the mandatory fields in the export:

"Issue Type"
"Description"
"Issue Key"

"Reporter"
"Summary"
"Resolved"
"Resolution"

In your CSV then edit all the values in the 'Resolution' column to what you need them to be (make sure they exist as resolutions in Jira).

If you then import this CSV back into Jira into the project, it will copy the values from the CSV over the issues in Jira and will update the Resolution.

Phil

[Jeanne ROBERT]

Hi thank you for your answer. I will try to update with a csv. Thank you

[Jack Brickey]

FWIW i really don't like this approach as it is sort of an unlocked backdoor and if not careful could result in undesirable updates to issues. But that is just me. :-)

[PhilSpo]

No i agree. Its a bodge job and Its more dangerous as you could edit issues by accident and cause more of a mess.

However the transition approach while it will work and set the resolutions, it would stamp 'resolved' as today's date. 

This is something we couldn't have because of our reporting methodology, All the issues had to keep the original resolved date. So the CSV upload was the only way to change resolution but keep resolved.

Phil