nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to bulk update the Resolved date field using CSV import when on Data Center platform

Brad Way

Hello I have found several articles that explain how to perform bulk updates to the resolution date field using CSV files but they are specific to the cloud platform.

Is it possible to update the Resolved date field using using a CSV file while on Data Center platform?

Accepted answers

Brad Way

Thank you all,

I was able to work with our admin to update the fields using the recommended articles.

All comments

Martin Runge

Hi @Brad Way,

Welcome to the Atlassian community!

Jira sets this field automatically through the workflow when a resolution is set on a transition, and the CSV importer does not let you overwrite it on existing issues.

The only way to change it afterward is directly at the database level. I would not suggest that, because it bypasses Jira’s logic, is not supported by Atlassian, and needs a reindex plus a solid backup to be safe.

If you need the original reporting dates, I would store them in a separate custom date field and populate it via a CSV update. That keeps your history intact and gives you a field you can use in filters and dashboards.

Tinker Fadoua - [Seibert US]

@Brad Way

How many issues do you have that require this update? You can run a query re-open the issues then field information will be wiped out.

Even though I am not into changing the resolution date unless there is a strong reason.

All the best,

Fadoua

Tomislav Tobijas

Hi @Brad Way

There's this (quite old) Community discussion where someone confirmed successfully updating the resolution date via CSV import on v8.22.6.

You might also find this one useful: Importing data from CSV — Jira Data Center 📚

On another note, do you have any AI tools or assistants connected to your Jira DC instance?

I've been using Rovo and AI tools connected through MCP with Jira Cloud to perform bulk updates simply by providing a CSV and instructions. It's been brilliant compared to traditional bulk editing!

If you have something similar connected to Jira DC, it might be worth exploring, although system-field restrictions would still apply.

Hope this helps! 🙂

Cheers,
Tobi

Mihai_LeanZero

Hi @Brad Way,

It can work on Data Center. The users who got it working mapped Resolution in the same import as the date, but reports are mixed, including in the 8.22.6 thread linked above, so I'd test a single issue first.

On JRASERVER-13035 a comment back in 2009 says the date only sticks when Resolution is mapped too.
https://jira.atlassian.com/browse/JRASERVER-13035

The CSV import doc also warns that an update import resets columns to their default values if they aren't in the CSV. Map Issue Key, Resolution and Resolved, plus any other field you'd want to keep.

If some resolved issues end up with an empty Resolved date, this KB fills it in from the transition history in the database (it won't set a date you pick). A re-index is needed afterwards.
https://support.atlassian.com/jira/kb/how-to-fix-resolution-dates-retroactively-in-jira-through-the-database/

Brad Way

Thank you all,

I was able to work with our admin to update the fields using the recommended articles.