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; } } }

Is there a way to change the "Resolution Date" in Jira?

Nicolo Chioato

Sometimes an issue isn't resolved in the moment of the pressure of the "Resolve Issue" button, but it could be a user resolves an issue in the day T and he presses the "Resolve Issue" button after 2 days. The Resolution Date showed is T+2, but I'd like to register T.

Is there a way to obtain T or must I create a custom field?

Thank You

Accepted answers

Nic Brough -Adaptavist-

No, the resolution date really is "the last time the resolution was set", it's not actually physical data, it's derived from the time the resolution changed.

As you suggest, you'll need a custom field.

Brad as Paul

In JIRA Cloud it is possible to update the resolution date by doing a CSV import.

Just export a CSV of the issues you need to update. Add a "resolved date" column, populate dates, then import into JIRA as Admin via External System Import.

Make sure to set the date formatting to match in CSV and import tool. Also include the issue-ID and summary in tour CSV. If the issues are also missing a "resolution" you will also need to update the "resolution" in the same import, otherwise the "resolved date" will not change.

All comments

Nic Brough -Adaptavist-

No, the resolution date really is "the last time the resolution was set", it's not actually physical data, it's derived from the time the resolution changed.

As you suggest, you'll need a custom field.

David Keaveny

If you were running the self-hosted version, and you had reliable backups, and you took the service offline first, you could edit the SQL in the underlying database, in which case it's the jiraissue.RESOLUTIONDATE field, but for OnDemand you're probably on your own.

Kyle Moseley _blueridge_cx_

Do you know of any ways to do this via scriptrunner?

Christopher Emerson

Very sad to find this out. We've had tickets on Cloud that accidentally don't get marked resolved and there is not even an admin-only way to fix them to show when they were actually resolved?! Wow. Embarrassingly bad design folks.

Nic Brough -Adaptavist-

Er, you're expected to not badly design your workflow, not botch fixes in later.

Brad as Paul

In JIRA Cloud it is possible to update the resolution date by doing a CSV import.

Just export a CSV of the issues you need to update. Add a "resolved date" column, populate dates, then import into JIRA as Admin via External System Import.

Dakotah North_wapahn

Wow ... that is a very unhelpful response.

Thats like saying that you’re expected to never make a mistake.

Viacheslav Starovoytov

Thanks Paul! Your example has just helped me change resolved dates in the cloud! It is like a magic )

Bill Miller_zzeo32

Thanks for this, I may try it out. I had on premises self-hosted at my last customer, but we're using Cloud here. Yay!! Really, thank you @Brad as Paul !!

Francois Toubol

It looks like it is Issue Key (as opposed to Issue ID), that needs to be used to map. When you do so in the wizard a message appears at the top saying "You have selected Issue Key mapping. Please note that importer will update existing issues matching the Issue Key from the CSV file."

The problem is: it does not work for "Date Resolved" for me...

Dario B

Thanks a lot everybody, I have verified that it is indeed possible to modify the "Resolved" field with CSV import and I have updated the below bug ticket for Jira Cloud:

- https://jira.atlassian.com/browse/JRACLOUD-65502

Camille_kwy92k

Pretty bad response from a community champion.

Modifying the resolved date is absolutely a feature that should be possible.

lnelson1

I'm going to go ahead and give it a try, but can anyone confirm if this will work for JIRA Server?

Ameya

This issue happened with me in a critical project when i had bulk changed the Resolution using script runner built-in functionality. The solution is for Jira DC and PostgreSQL. Please try the same on Lower environment before doing it Live. It works.

The steps are:

Spin up a copy of the Jira database backup from the latest version before the issue occured

Export the id and resolutiondate values to a CSV file:

\copy id, resolutiondate FROM jiraissue WHERE project = "PROJECT_ID" AND resolutiondate IS NOT NULL) to '/tmp/output-dev.csv' with csv;

Manually add a header of id and resolutiondate to the CSV.

Back up the potentially affected issues in the jiraissue table:

\copy id, resolutiondate FROM jiraissue WHERE project = "PROJECT_ID" AND resolutiondate IS NOT NULL) to '/tmp/prod-backup.csv' with csv;

Create a temporary table in Jira DB to house the updated value:

CREATE TABLE tmp_issues (id numeric(18,0), resolutiondate timestamptz);

Import issues from the CSV generated in step 2 to the table we just created:

\copy tmp_issues(id, resolutiondate) FROM '/path/to/output-dev.csv' DELIMITER ',' CSV HEADER;

Confirm this data looks correct:

SELECT * FROM tmp_issues limit 50;
<two columns with id and resolutiondate>
\d tmp_issues
               Table "public.tmp_issues"
     Column     |           Type           | Modifiers 
----------------+--------------------------+----------- id             | numeric(18,0)            | 
 resolutiondate | timestamp with time zone |

Update the issues using our temp table:

UPDATE jiraissue SET resolutiondate = tmp_issues.resolutiondate FROM tmp_issues WHERE jiraissue.id = tmp_issues.id;

Once this finishes, perform a rolling restart of Jira.
Drop temporary table:
```
DROP TABLE tmp_issues; 
```

Clean up jiraissue table:
```
VACUUM jiraissue; 
```

Perform a project reindex of Affected project.

Daniel Brvnišťan_m8r5gv

It is possible to use export/import in self-hosted instances as well:

search for the issues you want to edit
export to CSV (it's enough to export Issue key, Summary, Resolution and Resolution date fields)
use Excel to fill the Resolution and Resolved date
export to CSV UTF-8
import using External system import (CSV) - map Issue key (so it updates the correct issues) as well as Summary (mandatory) and your filled Resolution and Resolved date fields

Bill Tanner_a562kz

There is a way to do it in Jira Server. I know because I just did it, and it took a long time to figure out a viable solution. It is a little tedious, but you don't have to touch the backend database.

1) Create a new custom field as a placeholder for the resolution date. We used a Date Time Picker field.

2) In your CSV file, include a column with the resolution date for each issue you are updating. I set the format to "yyyy-MM-dd HH:mm:ss" (using the custom format function in Excel). I have found Jira to be very sensitive with the date format when doing CSV imports.

3) Via the External System Import function, import the CSV file. Be sure to set the date format to "yyyy-MM-dd HH:mm:ss". I match the Key and Summary, and match the Resolution Date in your CSV file to the new custom field you created in Step 1. Check the "Map Field Value" for the Resolution Date field.

4) Confirm the CSV import worked and your new field is populated

5) In your work flow, create a new recursive transition. Since these are all resolved issues, it should be from "Done" to "Done" or something along those lines.

6) On the new transition, add a post function where you copy the value from your new custom field created in Step 1 to the "Resolved" field. (Resolved is the system field that captures the data of resolution). We used the JSU add-on, and the post function "Copy Value From Other Field (JSU).

7) Do a bulk update, selecting all the issues you want to update the Resolved date. Execute the new transition you created in Step 6.

If you have any questions, feel free to reach out. This was a huge pain to figure out, but the solution is relatively simple (assuming you get the date format correct )

Bill Tanner_a562kz

We couldn't fill the Resolution date field directly via CSV import. In my post above, I provided steps to do it similar to those here, but we had to first create a custom field, fill it with the resolution date, and then copy that value over to the Resolved field.

Daniel Brvnišťan_m8r5gv

Interesting, I had those fields/columns in the CSV, and could select the system field in the mapping screen, no problem.

George Mihailoff

Surprisingly, this is a real issue. We decided to do something about it and released a resolution checker as part of our free addon (Quantify).

1. You can use JQL-powered search to lookup issues

2. Because we deal with things like time in status, throughput and other Kanban metrics we already know what resolution dates to suggest

3. Then selected items are available in the correct CSV format to use in the "External system import --> CSV"

Quantify Resolution Checker.png

Chris_7t6qi8

I can export my issue only as an XML or word. How can I import that to External System Import? It gives 3 options CSV, JSON and None. I chose None and tried to import word file. It is asking me for the delimiter of CSV file .

Dario B

Hi @Chris ,

Please notice you added a reply to a thread from 2012 and this is usually not advised.

I am not sure whether you are using Jira Cloud or Server, however, the way to export to CSV is showed in below screenshot:

I hope this helps. If not, please create a new thread for your issue.

Cheers,
Dario

Mario Alfaro

Thanks a lot, it still works. To import the CSV file you need to define at least 4 columns:

Issue Key, Resolution, Resolved Date, Summary

Daniel Soares_o2b83p

This was the final solution for me Thank you @Bill Tanner

tomh_8bdho6

Amazing stuff!
I used the solution from this thread and it solved all my problems

Thanks all

AP_ij8hk4

The challenge here is when the tickets are tied to a Workflow which doesn't allow you to transition the status out and back to some configured 'Completed' status. It's super convenient when searching for outstanding tickets using JQL to find all of those without an resolution (ie 'resolution = Unresolved', or conversely 'resolution != Unresolved' for those that are completed). So how to fix?

The easiest thing to do (only done this in cloud) to fix this is via a Jira automation, and should only take a minute:

Create a new Jira automation
Set the trigger to be manual and accept user input with a dropdown question
1. Optionally limit use to the desired user group(s)
Include the desired resolution system names in the options.
Add an 'Edit Issue' action and choose 'Resolution (System)' from the list.
Type the smart value name of user input field as the value as opposed to choosing one of the options. example:
1. ```
{{userInputs.resolution}}
```

Screenshot 2024-01-10 at 5.24.58 PM.png

Now when you find these tickets you can just run this automation!

Ignas Selvestravičius_b13wvr

Managed to update resolution and resolution dates. In my case, the problem was that I also mapped the issue ID and then the importer always skipped those issues. Without mapping the issue ID, but mapping the Issue Key there was no problem importing.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud