Hello, we are facing the same kind of problem, the resolution field is not updated when importing with CSV. we don't have any warning about it.

why is this bug stated as resolved whereas in comments we are still facing the issue ? (we are using the server version)

Guys, we just had a breakthrough after trying multiple times to import Date resolved and Resolution statuses.

The issue is that you NEED to have every Resolution field populated with data.
e.g. we only use Done, Unresolved and Declined for our cases. If we ignored the Unresolved statuses by leaving the fields blank, the whole import for this column would be ignored, breaking the Date resolved import also.

The problem here spans from the fact that Jira is not transparent at all with how this process is being handled, acting as if all columns were successfully imported (even though two of them fail). This case should at least trigger a warning that your columns weren't copied over, not to mention that a reason would also be useful.

This should be linked in:
https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

https://community.atlassian.com/t5/Jira-questions/Update-existing-issue-via-import/qaq-p/1291133#U1946867

https://community.atlassian.com/t5/Jira-questions/Whether-Jira-supports-updating-existing-issues-using-CSV-import/qaq-p/1008434

https://community.atlassian.com/t5/Jira-questions/Update-existing-issue-via-import/qaq-p/1291133

Hi iginzburg, Can you let us know the exact steps you followed and the error you got (if any)?

Another option would be to open a support request: https://support.atlassian.com/contact

It is not working. I still have the same problem

I have to disagree that this is "working."

If Atlassian doesn't want to change the behavior and make the resolution date act like every other field, that's fine.... but the import shouldn't report success with zero warnings or errors.  It should stop you from progressing with the import if the resolution date is mapped but the resolution state isn't, just like it stops you if the summary field isn't mapped. I'd call that "working," even if I continue to question the wisdom behind the intended behavior of this bug/feature.

This is now working in Cloud.

Only, the resolution dates are not imported/updated from CSV if you do not import/update the Resolution field as well. 

As per the "Is there a way to change the "Resolution Date" thread in the Atlassian Community, in order to update the resolution dates you need a CSV file with at least the below 4 fields:

1. Issue Key
2. Summary
3. Resolution
4. Resolved (to be mapped to "Date Resolved")

I am very surprised and disappointed this is a minor issue. I am in the process (after M&A activity) of migrating 3 companies and around 15 Jira Projects to Jira Cloud from a mix of on-prem and Jira Cloud - losing all the Resolved Dates renders vital reporting useless.

I am surprised this is viewed as a minor issue. We have recently migrated to Service Desk from Jira Software and this issue means that our historic SLA data is meaningless (when we had considered this a key feature).

I get exactly the same behaviour, so status "needs verification" can be changed to "yes, daniel verified it"