How do I remove resolved date when erroneously populated

Andrea Janoo

I am working in JIRA 6.4.  The issue I have is that the resolved date is populating on JIRA tickets in a couple of scenarios across 2 projects that have a similar workflow:

1. The ticket is created

2. The ticket transitions from one state to another

The date populated has been both a transition date and created, and recently when a ticket is moved from one project to another in the same instance, the original created date of the ticket is populated on the JIRA.  

I have tried bulk updating, importing resolved as blank and I have put a 'purge field' in the post function at each stage and have had no luck resolving the issue.  Any insight would be greatly appreciated

Petter Gonçalves

Hello Andrea,

Welcome to Atlassian Community!

I must confess that I did not understand exactly what caused your issues to have a wrong Resolved date populated, however, please allow me to give you some concepts about this feature so we can confirm we are in the same page here:

The resolved date is automatically updated in Jira issues when you set a resolution for it, and a resolution must be set only when the issue is transitioned to the last status of the workflow ("Done", "Closed", etc.).

That being said, the only way that would justify the resolved date of an issue to be corrected would be if the issue was transitioned to "Done" without being Done, by a mistake of the issue assignee. That was what happened? 

If that's the case, there are two ways to update a resolved date that was wrongly set:

1 - In case the issue is still not solved, you can simply reopen the issue and resolve it again when the time comes, so the issue will be set with the correct resolved time.

2 - In case the issue is already resolved by was wrongly transitioned to done before it was effectively resolved, you can import the correct resolved date using CSV import, as described in the documentation below:

Importing data from CSV 

P.S: 6.4 is a very old version of Jira, so maybe the steps above might not be applicable to it.

Let us know if this information helps.