Resolution set but Resolved date not and vice versa

[Ian Rees]

I am extracting some old Jira data and have noticed some issues with a Resolution but an empty Resolution date and vice versa, some issues with a Resolution Date but an empty Resolution.  I've tested scenarios move issues through transitions setting and unsetting Resolution and I find that if the Resolution is set, the Resolved date also gets set.  So what are the scenarios where one of those fields can get set, without the other ?

There is one outstanding scenario which I need to test and I am wondering if it is a result of a Workflow change and therefore migrating issues to new states and I am wondering whether Resolution and Resolution Date in that case can get decoupled. Any ideas?

[Matt Doar]

In normal operation, the code that sets a Resolution also sets a Resolution date. And clearing the Resolution clears the Resolution date.

But there is history here. For the first few years the Resolution Date was part of the Jira Toolkit plugin and not everyone used that. So some of your older data might be from when there was a Resolution but no Resolution Date. Or there were some manual changes in the database

For the other case where there is no Resolution, this can happen if users Move an issue to another project or issuetype and change the status to Closed. In that case the Resolution is not set. My suspicion is that this might be related to having issues with no resolution but with a resolution date.

I suggest cleaning up the data by adding a resolution date equal to the updated date, likely correct enough in most cases. And if there is a resolution date and no resolution, then pick a resolution and set it.

[Matt Doar]

For some context, we have about 9M issues and 1600 of those have a resolution date but no resolution. And 600 have a resolution but no resolution date. I'm not planning to fix this in our Jira unless I see evidence that it affects our users.

[Ian Rees]

That puts it in perspective because out of the several thousand rows I am importing, only 24 are mismatched in this way