How can I see the updated resolutiondate again?
Asked by Jhomilton Silva:

Hey guys,

When I use the created vs resolved gadget or when I use the time to resolution gedget, both use the resolutiondate filter which is no longer working, but in May it stopped being updated.

![02-Jira.png](/t5/image/serverpage/image-id/338180i930BC814492D3877/image-size/large?v=v2&px=999 "02-Jira.png")![01-jira.png](/t5/image/serverpage/image-id/338181i680887F5FACF4728/image-size/large?v=v2&px=999 "01-jira.png")Apparently, the settings are correct and we have not changed any points. How can I solve?


Answers:
author: Trudy Claspill
body: Hello [@Jhomilton Silva](/t5/user/viewprofilepage/user-id/5553627)

Welcome to the Atlassian community.

The Resolved portion of those charts will be based on the Resolved date/time field in the issues.

That field is set when the Resolution field is set in an issue.

Have you executed the filters used by the gadgets and reviewed the issues to confirm the Resolved and Resolution fields are set?

comments: author: Jhomilton Silva
body: Hello [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

Thanks for the answer!

<br />

Apparently the filter is correct. Because it always worked like that and suddenly it stopped working. This was the filter we used: project = xpto AND resolutiondate \>= 2023-10-01 AND resolutiondate \< 2024-05-05. Do you see any problems?


author: Jhomilton Silva
body: Do you know if there was any update with the resolutiondate field? I question this because it appears that it is not returning responses in the filter.


author: Trudy Claspill
body: Well, yes, there is a problem with your filter.

You are asking it to select issues that have a resolution date before May 5, 2024. The result will not include any issue resolved after that date.

project = xpto AND resolutiondate \>= 2023-10-01 AND   
++**resolutiondate \< 2024-05-05**++

If you want to include issues resolved after that date you need to change your filter.


author: Jhomilton Silva
body: I brought an example that wasn't cool. The filter is picking up to the most recent date. Therefore, it includes today, 07/29/2024. However, for some reason, in May, this filter stopped being updated.

It seems like there is a problem with the field that no longer captures the current date.

Even with this example, it doesn't update today. Here's the updated filter:

project = 16692 AND resolutiondate \>= 2023-10-04 AND resolutiondate \< 2024-07-30


author: Trudy Claspill
body: Can you provide a screen image showing an issue with the resolution date within the range, for an issue that is not being included in the results?

Can you reduce the data range, just for testing, to just a few days before the current date and show us the results of the filter?

Have you changed the output view of the filter to List and added the Resolution date as one of the columns to confirm what value the filter is seeing for the issues?


author: Jhomilton Silva
body: Sure!

As you can see, starting at the end of May, resolved cards stopped being counted. It is important to note that we do not change any filters.

I took a smaller break too. In the last 30 days and the same behavior remains.

![02-ultmos 90 dias.png](https://community.atlassian.com/t5/image/serverpage/image-id/338622iA3A06200768543DE/image-size/large?v=v2&px=999 "02-ultmos 90 dias.png")![01-ultmos 30 dias.png](https://community.atlassian.com/t5/image/serverpage/image-id/338621iE3BB0C06A4643A41/image-size/large?v=v2&px=999 "01-ultmos 30 dias.png")

1. project = 16692 AND resolutiondate \>= 2024-06-30 AND resolutiondate \< 2024-07-30

2. project = 16692 AND resolutiondate \>= 2024-04-30 AND resolutiondate \< 2024-07-30


author: Trudy Claspill
body: Thank you for that additional information. However that is not quite what I'm looking for.

> Can you provide a screen image showing an issue with the resolution date within the range, for an issue that is not being included in the results?

For this I want to see the details of an issue from project 16692 where the resolution date field is displayed and shows a date within the range specified in your filter. What I want to see is the breadcrumbs at the top of the issue, and the information in the red box.

![Screenshot 2024-07-29 at 11.03.17?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338634i674C0E70998B873B/image-size/large?v=v2&px=999 "Screenshot 2024-07-29 at 11.03.17?AM.png")
> Can you reduce the data range, just for testing, to just a few days before the current date and show us the results of the filter?

For this I want to see the actual filter and the results from the View All Issues screen. I wanted a smaller date range that encompasses just the past view days so you can show me the entire result set returned, including having the resolutiondate field and the created date field displayed as output columns.

![Screenshot 2024-07-29 at 11.08.50?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338635i4BBED6997EE56C81/image-size/large?v=v2&px=999 "Screenshot 2024-07-29 at 11.08.50?AM.png")


author: Jhomilton Silva
body: Got it, thanks for the explanation!

Here is the first evidence of the resolution on cards in red:

**01**

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

**02**

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

I found a difference between the cards. Even with a resolved status, in Jira, and the other as closed. Apparently, this is what is impacting the graph. Do we know how to fix it?

<br />

In addition, the following evidence is requested:

**03**

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

**04**

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


author: Trudy Claspill
body: Hello [@Jhomilton Silva](/t5/user/viewprofilepage/user-id/5553627)

PCE-944 is missing from the results because the Resolved (resolutiondate) field is not set.

That field is set when the Resolution field is set.

You can tell if the Resolution field is set by looking next to the Status button. The value of the field will be displayed next to the Status button as seen here.

![Screenshot 2024-07-29 at 3.19.48?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338693i6F157496114734BD/image-size/large?v=v2&px=999 "Screenshot 2024-07-29 at 3.19.48?PM.png")

You can see for PCE-944 there is not value displayed, which indicates the field has not been set.

![Screenshot 2024-07-29 at 3.21.10?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338694iCC530D5303E54DB3/image-size/large?v=v2&px=999 "Screenshot 2024-07-29 at 3.21.10?PM.png")

To Jira, that means the issue is unresolved, regardless of the Status assigned.

The field should be getting set during the transition to any Status that is color coded green (indicating a "done" status), and it should be cleared on any transition that can go from a green status to a non-green status.

Are these issues in a Team Managed project or a Company Managed project? I'm guessing that the issues are in a Company Managed project, because in a Team Managed project setting the Resolution field is usually handled automatically by Jira, without any intervention by users or custom configuration by administrators.

Fixing this is going to require assistance from a Jira Administrator in the case of a Company Managed project. The Workflow needs to be modified, and usually that can be done only by Jira Administrators.

If you want to attempt to set the Resolution field for issues resolved in the past and also try to set the Resolved Date to a date in the past, that will also require help from a Jira Administrator who would create a CSV file with the necessary information and use the External System Import function to import that file and update the existing issues.


author: Centro de Comando
body: Hi Trudy,

I work with Jhomilton and I'm one of our Jira Administrators.  

These issues belong to the same project and it hasn't changed from Team Managed to Company Managed or the other way around.

I'm looking in the workflow and I can't find anything related to the resolution field.

There was never anyone filling this field before, we don't know how it was filled and why it stopped being filled.   

Do you have other advice to gives us?

Thanks a lot for your help.


author: Trudy Claspill
body: Looking at the two issue images I can see that they are assigned different Status values; Resolvido and Fechada. The Resolvido status does not have the Resolution set.

Can you find any issues of the same issue type in the same project where the Status is Resolvido and Resolution has been set?

project=PCE and issueType = *"Insert Issue Type Here"* and status=Resolvido and Resolution is not Empty

If there are issues in the Resolvido status where the Resolution is set, you can examine the dates when those transitions occurred and look at what the status was before it transitioned to Resolvido. It is possible that the workflow transition to Resolvido was changed around that time, or the Resolution was set during the transition the issue was in prior to being set to Resolvido.

To fix the problem going forward you need to look in the workflow for the issue type(s) where the status is green/Resolvido and there is no value for Resolution.

You need to examine all the transitions to the Resolvido status and check the Post Functions for those transitions. They need to have a Post Function for setting the Resolution field. Here is an example of the Post Functions screen using the original Workflow Editor.

![Screenshot 2024-07-30 at 10.56.53?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338932i92EED12052E08B09/image-size/large?v=v2&px=999 "Screenshot 2024-07-30 at 10.56.53?AM.png")

Making the change to add that Post Function will not set the Resolution for issuess that are currently in that status. You can move the issues through a series of transitions and back to Resolvido to update the Resolution after fixing the workflow. That will show the issues as Resolved on the current date.

If you want to try to set the Resolution field and Resolved date to a date in the past that has previously been possible using a CSV Import operation. You can refer to this article, and extrapolate from it how to set the Resolved date and the Resolution field.

<https://confluence.atlassian.com/jirakb/how-to-change-the-issue-creation-date-using-csv-import-779160699.html>

However, on July 31 the current CSV Importer process is being sunset. I don't know if the new process will support the same functionality for updating issues vs. creating new issues during the import.


author: Centro de Comando
body: We are using Jira's standard workflows. We didn't create these workflows.  

I will take a look on the new info you sent and get back to you.  

Thanks again!


Tags: cloud

dashboard

gadget

jira-cloud