-20260720-211628.png?cb=88d11c151e6c4f8778fbcd5c20613ec0)
Issues in the Unmapped statuses column will not appear in the board or in reports created from it. This article explains how to display them by mapping these statuses to a board column.
Why should you verify if there are unmapped statuses?
-20260305-195446.png?cb=48f1e066a960bd85b058baac47dbcefc)
The screenshot above shows a report built from a board to display Backlog issues. No issues appear because items with a To Do status are not mapped to any column on the board.
As a result, these issues do not appear on the board and are not included in the report.
Once issues with a To Do status are mapped to a board column, they appear in the report, as shown in the following example.
-20260305-195514.png?cb=647e78ecbb323777140ed22a89d1ac96)
How can you add unmapped statuses to a board?
In the screenshot below, To Do issues appear in the Unmapped statuses column. Reports created from this board also exclude these issues.
To map a status, drag and drop a status from the Unmapped statuses panel to the appropriate column.
For more details, refer to the related article from Atlassian on editing board columns.
-20260305-195655.png?cb=c6f98c7351a2ac0de83c991774714296)
Both Project admins, Board admins, or Jira admins can map existing unmapped statuses to active board columns.
However, only a Project admin or Jira admin can add new statuses to a project's workflow. Board admins cannot create, delete, or modify workflow statuses.
How can you verify if other issues aren’t hidden?
Once you’ve completed the previous steps and still suspect that other issues are hidden in the board or report, follow the steps in the related article to review permissions for the issues referenced in the report source.
If you have questions or need assistance, contact our support team via email or service desk. Our team is available Monday through Friday (9:00 AM to 7:00 PM GMT+7) to help with technical challenges or discuss improvements.