I have a Kanban board. It has 218 items listed.
It has this quick filter:
"Release Plan" = Urgent
When I engage it, only one issue shows, which is correct.
But when I change it to this:
"Release Plan" != Urgent
No Issues show.
This is caused by a known bug in the Issue Navigator (which also manages the Quick Filters): https://jira.atlassian.com/browse/JRA-29179 - Issues with empty value won't be included in results of a negative search.
George, I know you went for labels already, but another workaround would be to change your filter query to "Release plan" != Urgent OR "Release plan" IS EMPTY
From a db point of view this isn't actually a bug :-)
It says: All issues with a value different from FooBar. But it doesn't have any value and any comparision with null is null :-)
I went for a new field, drop down, single select. And it is acutally more user friendly. The number of choices is small and this way the user only needs to update one field, not two. And the transition post can handle it.
Yes they are mapped.
Please understant that they DO show up when the filter is not applied.
All Issues = 218
Urgent Issues = 1
So my expectation is that All Issues that are not Urgent = 217
"<>" was not accepted.
But I have solved it:
I added a default choice to the field and set the value of the field to the default for all of the other Issues. Then I reindexed.
Looks like there was some problem from the field being empty for the other records.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events