How to Delete a Jira Board: A Step-by-Step Guide (2026)
Need a safe way to jira delete a board? Learn how to remove the board view without affecting projects or issues. Read now for the 2026 steps.
Deleting an unused Jira board can clear clutter, but one wrong click can remove a board your team still relies on. It’s easy to confuse a board with its project, issues, or saved filter, and those are not always affected the same way.
But here’s the truth: deleting a board removes the board view, not the underlying Jira issues or project. To do it safely, confirm you have board administration rights, identify the correct board, and check whether its saved filter supports anything else. Here’s a practical walkthrough for Jira Cloud, plus what to check if the menu looks different or you can’t find a delete option.
How to delete a Jira board safely
In Jira Cloud, open the board directory, find the board, use its More menu, and choose Delete. Check the board name before confirming; deleting the wrong board can disrupt a team’s routine even though its issues remain.
- Confirm which board you intend to remove. Open the board and check its name, project context, and columns. If several boards have similar names, ask the team which one is no longer needed.
- Check your permissions. You generally need board administration rights to manage or delete a board. If the delete option is missing, ask the board administrator or Jira administrator to review access.
- Open the board directory. In Jira, go to Boards and select View all boards. Find the board you want to remove.
- Choose the delete command. Open the board’s More menu, often shown as three dots, and select Delete. Review the confirmation message carefully.
- Confirm, then verify. Confirm only if the board name is correct. Return to the board directory and check that it no longer appears.
- Review the saved filter separately. A board uses a saved filter to decide which issues it displays. Check whether that filter is still needed by another board or report before removing it.

If the menu labels differ
Jira’s navigation can vary by product version, permissions, and interface updates. Look for the board directory, a three-dot menu, or board settings. If you still can’t find a delete action, ask an administrator to check your board role and the board’s ownership.
Quick checks before confirming
- Make sure the board name and project context match your intention.
- Tell teammates who regularly use the board that it is being retired.
- Check whether the saved filter is used by another board, report, or dashboard.
- Record any useful configuration details, such as column names or swimlane settings, if your team may need them later.
What deleting a Jira board changes—and what it doesn’t
A Jira board is a way to view and organize issues. It can show work as a Scrum backlog or a Kanban flow, while the issues themselves remain in their Jira project. Removing the board does not, by itself, delete those issues or the project.
Think of the board as a window onto work. Closing the window removes that view, but the work is still in the room. The saved filter behind the board is a separate item, so check its use before making any additional changes.
Board, project, issues, and filter are different things
- Board: A view that organizes issues into columns, backlogs, or other work stages.
- Project: The Jira space that contains and organizes project work.
- Issues: Individual work items, such as tasks, bugs, and stories.
- Saved filter: A query that determines which issues a board can display.
For example, a team may delete an old Kanban board while keeping its project and tasks active. If the board’s filter also powers a dashboard gadget, that gadget may still depend on the filter after the board is gone.
Why you might not see the delete option
The most common reason is permissions. Board administration rights may be required to change or remove a board, and simply being able to view it does not necessarily give you those rights.
Another possibility is that you are looking at the board rather than the board directory. Navigate to View all boards and check the board’s More menu. If it remains unavailable, ask the board administrator or Jira administrator to confirm who can manage it.
What to ask your administrator
Send the board name and link, explain why it should be removed, and ask whether other teams depend on it. This gives the administrator enough context to check ownership, access, and the associated filter without guessing which board you mean.
Should you delete the board or keep it for reference?
Delete a board when it is no longer useful and the team has agreed to retire it. If people may need to revisit its workflow, keeping it temporarily can be safer than removing it immediately.
For example, a team changing from a release board to a sprint board might keep the old board available during the first release cycle. After confirming that no one needs the previous view, the administrator can remove it and review its saved filter separately.
A simple decision guide
- Delete it when it is obsolete, the team has confirmed it is unused, and you have checked its filter.
- Keep it for now when it supports an active process or people still need to review its setup.
- Ask for a review when you are unsure who owns it or whether another team relies on it.
Jira board retirement is a small task, but a short check-in can prevent confusion. Tell affected teammates what will change and where they should go to follow work afterward.
How to avoid problems when retiring a board
A careful handoff reduces the chance that someone loses a familiar view halfway through a sprint. Before deletion, name the replacement board or explain how teammates can find the same issues in Jira.
It also helps to review dashboards and reports that may use the board’s saved filter. A board can disappear while a filter remains useful elsewhere, so treat board removal and filter cleanup as separate decisions.
Use a short retirement checklist
- Confirm the board is no longer part of an active workflow.
- Tell the team when it will be removed and what view replaces it.
- Check the saved filter for other uses before changing or deleting it.
- Ask an administrator to handle the removal if you lack board permissions.
- Verify afterward that active boards, reports, and team routines still work as expected.
A project management option beyond Jira boards: ONES.com
ONES.com brings project management and knowledge management together in one platform. ONES Project handles project and work management as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative. The products are sold separately, so teams can choose the part that fits their needs.

If you are reviewing Jira boards because a project workflow has become difficult to maintain, ONES Project offers Jira-compatible workflows and core planning capabilities. It can be worth evaluating when you want a more unified project setup, fewer add-ons, or a self-hosted deployment option.
Core capabilities
- Scattered project tracking → Jira-compatible workflows → Teams can use familiar workflow patterns while organizing work in ONES Project.
- Limited visibility into progress → built-in reporting → Project leads can review progress without assembling every update manually.
- Workflows that do not match team processes → custom workflows → Teams can shape work stages around how they actually deliver projects.
- Fields that miss important context → custom fields → Teams can track relevant details alongside tasks and issues.
- Sprint planning needs → sprint management → Agile teams can organize planned work and follow sprint progress.
- Repeated manual actions → automation → Teams can reduce routine work through configured rules.
- Too many separate project and knowledge spaces → ONES Project and ONES Wiki → Teams can select the project and knowledge capabilities they need within the ONES.com platform.
- Deployment restrictions → Cloud, On-Premise, Private Cloud, or Air-gapped deployment → Organizations can choose an environment that fits their operating requirements.
ONES.com offers a free tier for up to 30 seats. Its cloud and self-hosted versions have feature parity, which can matter to organizations that need to keep project management on-premise or in restricted environments.
Where it may fit
A team replacing an old Jira setup: A project lead can assess whether ONES Project’s workflows, sprint management, custom fields, and reporting fit the team’s current process. The goal is to reproduce necessary ways of working, not simply recreate every old board.
An organization aligning project work and knowledge: Teams can consider ONES Project for project management and ONES Wiki for knowledge management. Because the products are sold separately, the organization can evaluate each capability on its own terms.
ONES.com is a separate platform, not a setting inside Jira. If your only goal is to delete one obsolete Jira board, the steps above are enough. Consider an alternative platform when you are assessing broader workflow or deployment needs.
Common challenges when deleting a Jira board
The delete command is missing
Problem: You can open the board but cannot find a delete action. Solution: Check the board directory and ask the board administrator or Jira administrator to confirm your permissions.
You are unsure whether issues will disappear
Problem: The board displays active tasks, so deletion feels risky. Solution: Remember that removing the board does not itself delete the Jira project or its issues. Confirm where the team will track those issues afterward.
The saved filter may be used elsewhere
Problem: You want to remove everything associated with the board in one go. Solution: Treat the board and its saved filter as separate items. Check for other boards, dashboards, and reports that may rely on the filter.
Teammates still rely on the old view
Problem: The board looks inactive, but teammates may use it occasionally. Solution: Check with the team and give them a clear replacement or transition period before deletion.
FAQs about deleting Jira boards
Does deleting a Jira board delete its issues?
No. Deleting a board removes the board view, not the Jira issues or the project that contains them. The issues remain in Jira and can still be accessed through other boards or project views, subject to each person’s permissions. Before deleting a board, tell the team where they should go to follow the work afterward.
Can I delete a Jira board without being an administrator?
You may need board administration rights to delete a board. The exact permissions available to you can depend on how the board is managed and your Jira setup. If you can view the board but cannot find a delete option, ask the board administrator or Jira administrator to check your access.
Does deleting a board also delete its saved filter?
Do not assume that removing a board also removes its saved filter. A filter can be useful to other boards, reports, or dashboard gadgets. Review the filter separately and check whether anything else depends on it before changing or deleting it.
Can I restore a Jira board after deleting it?
Do not count on a simple restore option. If you may need the same board setup again, record useful details such as its columns, workflow arrangement, and filter query before removal. An administrator may be able to help recreate a board, but recreating it can take time and may not reproduce every setting exactly.
Conclusion
To delete a Jira board, find it in the board directory, use its More menu, and confirm the deletion. First check your permissions, identify the right board, and review whether its saved filter supports other work.
Deleting an outdated view can make Jira easier to navigate, but a brief team check prevents avoidable disruption. If you are retiring one board, follow the steps above. If you are reconsidering how your organization manages projects more broadly, compare your workflow needs with options such as ONES Project.