TL;DR. Anyone know why a Kanban board would silently fail to load issues that match its associated Filter Query?
For some reason, my Kanban board is empty, despite its Filter Query matching lots of issues and being shared with all project roles. There are no errors in the browser console and all network requests after a hard page refresh are coming back with OK status. Other members of the project are also having the issue.
I've tried updating the Filter Query to be a simple `project` match, to no avail.
This is an Atlassian-hosted JIRA instance, so we have not (and cannot) make low-level changes or access the underlying database.
That was totally it.
We've been removing unused fields, and this was one of those fields.
Emptying this sub-filter resolved our issue.
**Follow-up:** I'm curious *why* this causes the query to silently fail. If anything, I would expect it to have no effect, since fixVersion would technically be empty. And if fixVersion isn't a valid field, I would expect the query to fail loudly.
Nope. No active quick filters, but good call on checking into that.
FWIW, I went into the board's Columns configuration and dragged one of the status over to create a Backlog, to see if the Backlog is affected, too. As it turns out, yes, the Backlog is affected in the same way (empty list of issues, despite its Filter Query matching plenty of issues).
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
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