Newly created/updated issues intermittently invisible in Backlog board view, despite existing and ma

[jarco]

For about a week, newly created or updated issues in one of our company-managed Scrum projects stop appearing in the project's Backlog board view, even with all board filters cleared and searching by the exact issue key. This started happening right after completing a sprint with ~23 issues, and has recurred with multiple newer issues since.

Reproduction / evidence:

- The affected issue is a Bug-type issue, created today, assigned to the currently active sprint.

- Fetching the issue via the Jira REST API (searching by project + exact key) returns it correctly with all expected fields (correct project, status, sprint field set).

- Opening the issue directly by its URL works fine and shows all the correct data.

- In the Backlog board view, with all filters (Version/Epic/Type/Label/Quick filters) cleared and searching the exact issue key in the board's search box, the issue does not appear in any sprint section or the Backlog section at all (0 matches out of 500+ total items in the project).

- This is not an isolated case - it has happened with multiple new issues over the past week, not just this one.

- We already checked the board's column-to-status mapping (Board settings > Columns) to rule out the issue's status being mapped to a "Done"/last column, and that is configured correctly.

Impact: We can't track or plan newly created work through the Backlog view, and have to rely on direct issue links or JQL search in the meantime.

Has anyone else seen this, and is there a known fix?

[jarco]

I found out that is was none of the options mentioned. What ended up resolving the issue was to delete stale work items from the backlog. So reducing the amount of work items on the backlog allowed the new work items to appear again.

[Pallavi Shirodkar]

Hi @jarco 

Can you please check this once, this likely relates to filter or status mapping issues, security levels, or a Jira indexing problem. To fix this, check the board's filter query, ensure issue statuses are correctly mapped and visible, verify security levels, and consider reindexing Jira.

Hope this helps.

[Brita Moorus]

That definitely doesn't sound like expected behavior.

A couple of things I'd check:

• Does the issue match the board filter JQL (not just the project)?
• Does it appear on another board using the same project?
• Are all affected issues in the same status and is that status mapped to a board column?
• Does the issue appear after a few minutes or is it permanently missing?

Since the issue is returned by the REST API and opens correctly, it sounds more like a board rendering/indexing issue than a problem with the issue itself. If it's affecting multiple newly created issues over the past week, I'd raise an Atlassian Support ticket - they can investigate whether there's a backend indexing or board synchronization issue.

Hope this helps! 💙