In Jira, tasks get crossed out even when not resolved. Seems very random

I'm using JIRA version v6.3.15. We upgraded recently and since then issues seems to be crossed out on JIRA boards even if they are still in progress and their resolution is "unresolved".

1 answer

1 vote

There's a usual culprit for this one, and if it is what I think it is, you need to perform the first step on this list immediately to stop the damage expanding

As an admin, go to Admin -> Issues -> Resolutions.   This is a list of available resolutions for your system.  Find the one called "unresolved" and delete it.  Now.

This will stop things getting worse.  Your next exercise is one in clearing up the damage that has been done, but I won't talk through that until we can confirm that my guess about the root of the problem is correct.

Thanks for the help. When trying to do what you suggested Jira asks me to give a new resolution for the issues already marked as unresolved. Any suggestions on what to do with that?

Ah, good point. You need rid of that resolution because it's utterly wrong and has caused damage, but moving it to another resolution may not be the best move at the moment. So, as you've been able to confirm that "unresolved" is the problem, I would 1. Rename "unresolved" as something clear like "this is a broken resolution, do not use me" 2. Analyze *why* someone has broken your system. My best guess is that someone put the resolution field on an edit screen, realised that they'd done something dumb, and then added a broken resolution instead of removing the field. So, I'm afraid what you need to do is go through *every* screen in your system and check if it has the resolution field on it. When you find a screen that does have the resolution on it, you then need to look at where it is used. If the screen is ONLY used on transitions that go INTO a status that you consider to be "done" (i.e. "resolved", "closed", "rejected" type status), then it is fine. If the screen is used for VIEW, it's fine. If it is used for EDIT, or transitions that end in any "open" type status, then *delete the resolution field* from the screen. 3. Now we can start to repair the data - do a search for "resolution = this is a broken resolution *and* status in (your closed status list)" - this will give you the extent of the damage I'll actually stop there, because the next step in fixing this is dependent on the size of the problem. If you run through those three steps and let us know the size, we can move on.

Hello from a year and a half in the future, 

I did the above and indeed there is a resolution field in an Edit screen (one screen used for all sad)

and searching for Unresolved resolution and status Done returned ~900 issues... 

Is there a way to set them to a proper resolution?

Thanks in advance

There's a script in the script-runner that can fix them, but if that's not an option, you'll need to cycle them through a workflow transition with "clear resolution" on it.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,305 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot