Show past tasks as completed and edit schedule dates (JIRA Cloud)
Asked by Matt Bourne:

I have imported tasks that have already been completed. I want them to appear on the chart. But they are being marked as not complete even though they have a status of done?

<https://www.awesomescreenshot.com/image/3566963/f82e17573855656ab2d204680c86686d>


Answers:
author: Petter Gon?alves
body: Hello Matt,

I believe that you're facing an index problem here. Have you already tried to re-index your JIRA after the import?

Also, I believe that maybe the **integrity checker** would fix any possible errors in the database parameters.

Please, try both procedures (Not at the same time) and check if it corrects the problem.

**Please Note:** We **strongly** recommend taking a backup of your data before correcting any data inconsistencies.

If both procedures above does not fix the issue, I recommend you to apply the workaround provided before in a **single issue**and check if it will fix the problem:

<https://confluence.atlassian.com/jirakb/how-to-edit-the-resolution-of-an-issue-313467778.html>

comments: author: Matt Bourne
body: I should have said (title now edited) that I am on cloud so I cant use the integrity checker or indexer.


author: Petter Gon?alves
body: Hello Matt,

In that case, I recommend you to try the workaround suggested before and check if it fixes the issue.

If the problem keeps happening, please open a ticket with our support team so they can further investigate it:

<https://support.atlassian.com/contact/>


author: Matt Bourne
body: So all my resolutions are done. This happens automatically when status becomes done. So im not sure I follow.? Do you think if I use this workaround to change the resolution to 'anything' it might force something to update in the background?


author: Petter Gon?alves
body: You're correct, Matt.

I believe that for some reason, the system is not recognizing your imported issues with a valid resolution, so a manual update on resolution must probably set the correct resolution.

I also would like to clarify a few things:

- Is the problem happening for all issues in your system? Or only for the ones you imported?

- How did you configure the JQL to return the done issues to reproduce the problem?


author: Matt Bourne
body: So the strange thing is that none of my issues are listed as done.

<https://www.awesomescreenshot.com/image/3569855/bce188fda62967e7e6a8c8b6669a527d>

Not just the few I imported so I could set the completed date in the past. But all the issues since we've been using JIRA for the last few months.


author: Matt Bourne
body: and yet if I do a JQL search for done o resolution I get

<https://www.awesomescreenshot.com/image/3569868/9fee35e36aa545781a091cf1817eb84d>


author: Petter Gon?alves
body: That's a really strange behavior, Matt.

The only possible root cause that I can think without further investigating the issue is that maybe someone has configured a custom field and named it as **Resolution** instead of using the correct system field.

Can you check if you more than a single **Resolution** field?


author: Matt Bourne
body: No I don't but it looks like I may have custom status field. But surely there are protections against that? Investigating further.


author: Petter Gon?alves
body: Hello Matt,

Can you check if you have properly added a valid **Resolution** for the Tasks you imported?

Most of the reports on JIRA only consider an issue resolved when the **Resolution** is properly configured, not mattering the **Status** of the issue.

If that's the case, you can follow the workaround mentioned in the documentation below to fix it:

<https://confluence.atlassian.com/jirakb/how-to-edit-the-resolution-of-an-issue-313467778.html>

comments: author: Matt Bourne
body: I think this is the issue but it it showing as resolved = done <https://www.awesomescreenshot.com/image/3567350/152f805fe5988f6272f929140f93e1ca>

However when I search by done issues in the filters nothing is showing..


author: Petter Gon?alves
body: Hello Matt,

I believe that you're facing an index problem here. Have you already tried to re-index your JIRA after the import?

Also, I believe that maybe the **integrity checker** would fix any possible errors in the database parameters.

Please, try both procedures (Not at the same time) and check if it corrects the problem.

**Please Note:** We **strongly** recommend taking a backup of your data before correcting any data inconsistencies.

If both procedures above does not fix the issue, I recommend you to apply the workaround provided before in a **single issue**and check if it will fix the problem:

<https://confluence.atlassian.com/jirakb/how-to-edit-the-resolution-of-an-issue-313467778.html>


Tags: advanced-roadmaps