How to Fix Jira Board Not Showing [All Issues or Specific Issues]

In this tutorial, you'll learn about How to Fix Jira Board Not Showing [All Issues or Specific Issues]. We cover key concepts, practical examples, and best practices.

Jira boards display issues based on a saved filter. When the board does not show all expected issues, the underlying filter is too restrictive, column status mapping is wrong, or a board sub-filter is hiding certain issues.

The Problem

You know issues exist for a project, but they do not appear on the Scrum or Kanban board. Some issues are visible while others — with the same status — are missing.

Wrong approach — recreating the board from scratch.

The Fix

Check the board's saved filter:

1. Board → Board settings → General
2. "Saved filter" — the JQL query that defines which issues appear
3. Click "Edit" and verify the query returns all expected issues
4. Test the JQL in Issues → Search to see the complete result set

Check the board column mapping:

1. Board → Board settings → Columns
2. For each column, verify the mapped statuses
3. Issues in statuses not mapped to any column will not appear
4. Add missing statuses to the appropriate column

Check for board sub-filters:

1. Board → Board settings → General
2. Scroll to "Sub-filter" — this additional JQL further restricts the board
3. If present, it ANDs with the saved filter, potentially excluding issues
4. Remove or modify the sub-filter

Expected output:

Board shows all issues matching the expected criteria
Column counts update correctly
Dragging issues between columns updates statuses

Prevention Tips

• Test the board filter JQL in Issue Search before saving it to the board
• Map all active statuses to board columns, not just the ones currently in use
• Avoid using sub-filters unless you specifically need to exclude certain issues
• Use the "View as board" option from an issue search to test JQL as a board
• Review board configuration after workflow statuses are added or removed

Common Mistakes with board not showing

1. Using return to exit a function early instead of wrapping a pure value in the monad
2. Mixing let bindings with <- bindings in do notation, producing type errors
3. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors

These mistakes appear frequently in real-world JIRA code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Related: DodaTech's Jira Board Auditor reviews board configuration, filter JQL, and column mappings to identify why issues may be missing from sprint boards. Use with DodaZIP for configuration backup.