Is there a way to copy the "Resolution Date" to the "Closed Date"?
Asked by Mark L.:

We moved one issue type to another in a given Jira project. As part of the process we had to change the status from CLOSED-ABC to CLOSED-XYZ. In doing so the system reset the "Closed Date" field value to the day we made the change.

How can we get back our original "Closed Date" from the CLOSED-ABC status??

I was thinking one solution would be to copy the "Resolution Date" (which has not changed and is still displaying the CLOSED-ABC date in the Jira issue) to the "Closed Date" field. Is this possible?

Looking for some help as we use eazyBI to graph our Jira metrics and it uses the "Closed Date" and easyBI does NOT allow us to import the "Resolution Date".


Answers:
author: Samuel Gatica
body: Hi [@Mark L.](/t5/user/viewprofilepage/user-id/5576880)

Welcome to the community!

You can achieve this through automation by copying the Resolution Date to the Close Date field using smart values. Here is an example:

Tigger: Manually

Action: Edit Issue

Select Close Date and set field to {{issue.resolved}}

![Screenshot_1.png](https://community.atlassian.com/t5/image/serverpage/image-id/343883iE5C0849D29CE3115/image-size/large?v=v2&px=999 "Screenshot_1.png")

Hope this helps!

Best regards

Sam

comments: author: Mark L.
body: Thanks Samuel !!

Yes, setting up an Automation rule is a good way to copy one field value to another using a trigger (even a manual trigger). I tried to copy the "issue.resolution" field value to the "End Date" but that doesn't seem to be the Jira field that eazyBI uses to determine the Measures value of "Issues closed". I have reach out to the easyBI community to see if they can tell me which Jira field "Issues closed" uses in Jira to collect the measures. So far no response.

Regards, Mark


author: Ilze Krauze
body: Hi [Mark Lloyd](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5576880), and welcome to the community!  

"Resolution date" is a Jira default field that eazyBI imports automatically. Although this field is not available for editing in Jira import options, it is always available for analysis as a predefined issue property named "Issue resolution date." This property is used for grouping data in various measures, such as "Issues resolved," "Average resolution days," and others. For more details, you can refer to the [eazyBI documentation](https://docs.eazybi.com/eazybi/data-import/data-from-jira/jira-core-measures-and-dimensions).  

If you have any additional questions, please don't hesitate to ask.  

Kindly,  
Ilze

comments: author: Mark L.
body: Thanks IIze


author: Mark L.
body: Hi IIze,

Might you know the Jira field that eazyBI imports to collect the measures associated with eazyBI Measures- "Issues closed"?

In eazyBI, "Issues Resolved" seems to be different than "Issues closed".

Regards, Mark


author: Ilze Krauze
body: Hi Mark,

"Issues closed" can indeed differ from "Issues resolved" because "Issues closed" relies on the issue's **closed date**, which is calculated within eazyBI and based on the closed statuses specified in the eazyBI Jira import options ([https://docs.eazybi.com/eazybi/data-import/data-from-jira/issues-closed-measure](http://%20https://docs.eazybi.com/eazybi/data-import/data-from-jira/issues-closed-measure)).

When closed statuses are specified, the eazyBI import process analyzes the JIRA issue status change log to identify issues currently in one of the closed statuses. The process then determines the last transition to any of these closed statuses to establish the issue's closed date. If multiple statuses are defined as closed, the issue's closed date will be the **latest date** when the issue transitioned to any of those closed statuses.

Kindly,  
Ilze


Tags: closed-date

data-center

jira-data-center

resolution-date