Can you retroactively update resolution field?

[Brianna Barnes]

Recently we discovered that the resolution was not set in many of the workflows that we've created. We've since fixed the resolution issue. But it seems we have no "resolution" statistics since we started using those workflows. I want to see if there is a way that we can retroactively update the resolution to match the date that the ticket was put into a "resolved" status.

[Natalie Bateman · Accepted solution]

Hi Brianna, 

I have the same issue where the resolution is not set in my workflows.  Can I ask how you managed to resolve the issue?

Thanks

Natalie

[Petter Gonçalves]

Hello Natalie,

You can follow the instructions in this documentation to know how you can Bulk set the resolution of your issues:

1. Backup your instance.
2. Copy the workflow for the affected project.
3. Add a transition for the affected status(es) called 'Fix Resolution' with the destination as the step it originated from (so it doesn't change the status).
4. Add the 'Update Issue Field' post-function to that transition, as in the example below:
   
5. Make sure the transition has been configured to fire Issue Resolved event to get Resolution Date set properly.
   
6. As in our Configuring workflow schemes, add a new workflow scheme and associate the appropriate Issue Types to the new workflow.
7. Modify the project so that it uses the new workflow.
8. Using a Bulk Operation to edit those issues using the 'Fix Resolution' transition. This will reset the field to None.
9. Change the project back to the original workflow.

Let me know if this information helps.

[Petter Gonçalves · Accepted solution]

Hello Brianna,

The resolved date can be changed by import, however, the history of the cannot be changed.

Here are the steps to perform it:

- Export the issues (CSV format) which resolution was wrongly added after the change to status resolved 

- Get the data the issues were change to the status

- Change the field resolved on the CSV file to the correct one

- Import the CSV file again, properly mapping the issue-key field

Let me know if it helps.

[George Mihailoff]

There is a way to retroactively update this -- our free addon (Quantify) has a special "resolution checker" tool. Because we deal with things like time in status, throughput and other Kanban metrics we have the data to fix this.