Issues with No Resolution Not Showing Up with the Unresolved Filter

[Country Sam]

When I click on the "My Open Issues" filter, it brings up the Resolution filter as "Unresolved". However, none of the new issues I've created (all which have a blank resolution value) show up when I select "Unresolved". If I delete the Resolution value filter, all my issues show up. How can I get these blank resolution issues to correctly show up as "Unresolved"?

[Nic Brough -Adaptavist-]

This is a long-shot, but could you log in as an admin, go to Admin -> Issues -> Resolutions and look at the list that is set up?

Is "Unresolved" listed there?

[Randy]

Worth checking.  I didn't suggest that because his screenshot of one example shows the Unresolved in italics which wouldn't be the case if there was a resolution called Unresolved.  

Also resolved should be set with a date if that were the case also.

[Nic Brough -Adaptavist-]

You'll still see that on "proper" unresolved issues even if there is one.  I just want to completely rule it out!

[Country Sam]

No. No "Unresolved" resolution has been added to the resolution list.

[Nic Brough -Adaptavist-]

Excellent, thank you.

Well, actually, not excellent in terms of working out what is wrong.  Excellent in that you've completely ruled out the usual problem, so we can focus on the less frequent ones, but not good because it does not solve the problem.

Could you pick on one of the affected issues ( Prod-5075 would be ideal, as we've seen its current state) and compare the issue view with a search view that includes it?  Then, more importantly, re-index the project and check the two views again?

(Please note, this is even more of a long-shot than before, I don't expect much.  I'm checking minutiae before Atlassin can confirm bugs)

[Randy]

Did atlassian give us back the ability to re-index?  I thought they removed that ability on cloud?

[Nic Brough -Adaptavist-]

Ah, I forgot, Cloud, yes, you can't re-index still.

You can force an issue to be re-indexed though - edit it (just add a . to a text field or something)

[Randy]

Thanks for the tip nic! didnt realize that.

[mayank singh choudhary]

Hi
Any solution of above problem, i am also facing same issue.

[Kathy Hart]

This is going to sound unrelated, but . . . it may be that you have too many ticket types available in your project. 

I had newly created tickets that did not show up in the Open Tickets filter just like you. They were in a project that I use for testing all the tickets types with all different kinds of workflows and screens etc. 

The issue only seemed to affect Document ticket types for which I was building a new workflow. I tried everything to fix the workflow. They were newly created tickets so there was no resolution set. They clearly showed unresolved, but would not show up in the filter. 

I had an issue once before using a default issue type scheme that showed every ticket type that was ever invented as part of the scheme. It reached a point where it wouldn't show all the ticket types. 

So . . . 

In my project with the unresolved ticket problem, I decided to cull down the available ticket types in half. 

And PRESTO . . . 

The tickets I had created before are now showing up in a filter for all open tickets. 

That fixed my problem. I hope it helps with yours. If there are any ticket types you don't use, remove them from your Issue Type Scheme in Admin. 

[Randy]

Are you saying that if you uncheck that checkbox in the screenshot, you see issues with blank resolutions?  Can you screenshot an example of one?  

[Country Sam]

Yes. That's exactly the case. See the screenshot below.

[Randy]

Seems like a bug with Jira.  Can you try adding the Resolved field as a display column and see if there's any value set there for those 3 issues?  

[Randy]

Another thing to check would be to clear the assignee check (the 4th item that says Current User) while keeping Unresolved checked.  If issues return then that could help narrow down the issue.

[Country Sam]

If you look at the screenshot, "Resolution" is already a display column and no data is displayed in the column.

The "Assignee" filter has nothing to do with the issue. It all works properly and displays as it is supposed to. If I uncheck the "Assignee" field, it displays the several hundred issues assigned to other users.

Also, to note, the "Unresolved" issue only seems to apply to these new issues I've created as part of my new workflow. There's other issues that exist that filter correctly based on the "Unresolved" filter.

For example... see the attached screenshot. Other issues created through other workflows correctly show the "Unresolved" resolution. It has nothing to do with the Assignee of the field.

[Randy]

Resolved is different from Resolution.  It's a date field.  I'm wondering if it got set and is considered as part of checking resolution.  I dont think it does but it would be something to check.  Resolved is set automatically when resolution is set.

[Randy]

By chance is resolution being set to an empty string via some script or default setting on create?  Resolution being set to an empty string would be different from resolution being unset.

[Country Sam]

I just added the "Resolved" column an it shows blank.

[Country Sam]

There's no additional script that has been added and I haven't added any settings I'm aware of that should be changing the value of Resolution.

The only post functions on the create are the standard ones:

1. Creates the issue originally.
2. Move up Move down Edit DeleteRe-index an issue to keep indexes in sync with the database.
3. Move up Move down Edit DeleteFire a Issue Created event that can be processed by the listeners.

Additionally, to note, as an experiment, I tried adding the "Update Issue Field" post function to the "Create" transition and setting the "Resolution" to "None" and also tried adding the "Clear Field Value" post function  to the "Create" transition for the "Resolution" field. Both ended up with the same result as without.

[Randy]

Sounds like a bug with Jira or maybe an indexing issue.  Have you opened a ticket with atlassian support?  

[Country Sam]

If it was a bug in JIRA, I feel like the other issues created in this instance of JIRA would be doing the same thing rather than just the issues created in my specific project/workflow.

I lean a bit towards it being more something that I'm doing wrong rather than a bug. But, I'm also opening up a ticket with Atlassian Support as well.

[Josh_Kochelek__Modus_Create]

@Country Sam - Have you found a solution here? If not, what's going on with the new workflow? Does it have ANY interaction with the Resolution field? Any post-functions clearing the resolution?

Also, is this workflow for a new project or an existing project? Are the project/issue types that are associated with the new workflow using a new or shared field configuration scheme?

Also have you edited the resolution values at all? Or are they out of the box? 

If it's not a bug, then maybe there is something new/different about these issues. Just trying to hash out what that is.

[Kathy Hart]

I also have newly created tickets that do not show up in the Open Tickets filter. I'm using a custom workflow, but I don't have any resolution settings triggering then the issues are created.

Those tickets will not show up in any search with any resolution selected, so the tickets are not "set" to a specific resolution. They will not show up if you use the advance "resolution is EMPTY" search either.

Removing the Resolution filter from the query lets them show up on the list. Apparently this is a bug. Is there Support ticket on this issue yet?