Deleting a Board in Jira: Step-by-Step Guide and Checklist
Ready to remove an outdated board? Learn safe steps for deleting a board in Jira and what to check first. Read now.
An old Jira board can clutter your workspace, confuse teammates, or expose a view that nobody should use anymore. Deleting the wrong board can create a different problem: your team may lose a useful view, shared access may disappear, or you may mistake the board for the issues it displays.
But here's the truth: a Jira board is a way to view and organize work, while the issues usually live in projects. Removing the board does not normally remove those issues, but you should still check what the board displays and who relies on it.
Here’s a safe way to delete a Jira board, confirm the result, and avoid removing something your team still needs. I’ll also give you a practical checklist for checking permissions, filters, and shared access before you proceed.
How to Delete a Board in Jira: Step-by-Step
The usual process is to open the board’s menu, choose its deletion option, and confirm. Jira’s menus can vary by product version and permissions, so use the route that appears in your workspace.
- Check that the board is no longer needed. Ask its owner and regular users whether they still rely on it. Check for active sprints, recurring meetings, or team links that point to the board.
- Confirm you have permission. Look for the board administrator or board owner in the board settings. If you cannot see a delete option, ask the owner or a Jira administrator to handle the removal.
- Open the board’s action menu. In Jira Cloud, open the board and select the three-dot menu or board actions menu. Depending on the interface, you may also find boards through View all boards.
- Choose the deletion option. Select Delete board or the equivalent option shown in your Jira version. If the option is missing, do not try to work around permissions; contact the board owner or administrator.
- Review the confirmation prompt. Check that the board name is correct before confirming. This is especially important if several boards have similar names.
- Verify the result. Return to the boards list or open the board link. Confirm that the intended board is gone and that the relevant project issues remain available through other views.
Let me explain: a board generally displays issues selected by its filter. Deleting the board is different from deleting a project or its issues, but the saved filter may remain and should be reviewed separately.

What to Check Before Removing a Jira Board
Start with ownership and usage. A board that looks inactive to you may still support a release review, a support rotation, or a weekly planning session. Ask the people who use it before removing access for the whole team.
For example, a team may stop using a Kanban board daily but still rely on its saved view during monthly planning. Checking its recent use and asking the owner can reveal that the board should be kept, renamed, or archived from team navigation instead.
Next, note the board’s name, type, owner, and associated filter. This gives you a simple reference if you need to explain the change or investigate a missing view later.
Board, Filter, Project, and Issues: Know the Difference
A Jira board is a view of work, often organized into columns or sprint groupings. A saved filter determines which issues appear, while projects and issues hold the actual work your team tracks.
Here’s why this distinction matters: removing a board should not be treated as removing the work shown on it. A team can often continue viewing the same issues through a project page, another board, or a different saved filter.
Do not assume that deleting the board also deletes its saved filter. Check the filter separately after board removal, and leave it in place if another board, dashboard, or teammate still depends on it.
How to Confirm the Board Is Gone Without Disrupting Work
After deletion, check the boards list and, if relevant, try the old board link. Then confirm that the team can still reach its active issues through the project or another agreed view.
A useful example is a Scrum team removing a retired sprint board. The team can verify that the board no longer appears while checking that open issues remain accessible through its current project view.
If someone reports that work has disappeared, first check whether they are using the deleted board link. Look for the issues in the project or another suitable view before assuming that the issues themselves were removed.
Jira Board Deletion Checklist
Use this checklist immediately before confirming deletion. It helps catch common mistakes without turning a quick cleanup into a lengthy project.
- Confirm the board name and type.
- Ask the owner or regular users whether the board is still needed.
- Check for active sprints, recurring meetings, and shared links.
- Confirm that you have permission to delete the board.
- Identify the saved filter and check whether anything else depends on it.
- Confirm that the project and issues remain accessible through another view.
- Tell affected teammates where they should find the work afterward.
ONES.com Solution for Coordinating Project Work
Deleting a Jira board is a small administrative task, but teams also need clear ways to manage work, workflows, and project knowledge. ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

Value Proposition
ONES Project helps teams organize projects with configurable workflows, sprint management, and reporting. Its Jira-compatible workflows can help teams familiar with Jira move to a different project environment while retaining familiar ways to track work.
Core Capabilities
- Work scattered across project views: ONES Project supports project management workflows → teams can coordinate work in a consistent project environment.
- Difficulty adapting Jira habits: Jira-compatible workflows help teams retain familiar process patterns → onboarding can feel more straightforward.
- Rigid issue handling: Custom workflows and fields let teams shape work tracking → teams can reflect their own stages and requirements.
- Sprint planning overhead: Sprint management supports planning and tracking → teams can organize iterative work in one project environment.
- Limited visibility into progress: Built-in reporting offers project views → teams can review progress without relying only on manual status updates.
- Repeated administrative actions: Automation supports routine workflow actions → teams can reduce recurring manual steps.
- Too many add-ons to maintain: Native capabilities can reduce reliance on plugins → teams can simplify parts of their project setup.
- Deployment constraints: Cloud, On-Premise, Private Cloud, and Air-gapped deployments are available → organizations can select an environment suited to their requirements.
ONES.com provides full feature parity between its cloud and self-hosted versions. Its free plan supports up to 30 seats, which gives smaller teams a way to evaluate the platform.
Application Scenarios
A Jira team reviewing its project setup: A team can assess whether its current workflows, custom fields, sprint management, reporting, and automation meet its needs. If it evaluates ONES Project as a Jira alternative, it can compare those requirements with the platform’s native capabilities and deployment choices.
An organization with restricted network requirements: A team that cannot use a standard cloud deployment can consider On-Premise, Private Cloud, or Air-gapped deployment options. The organization can review its operational and security requirements before choosing an environment.
Common Challenges When Deleting a Jira Board
- The delete option is missing. You may not have board administration rights, or your Jira version may place the action elsewhere. Check the board owner and ask a Jira administrator to confirm your access.
- Teammates can no longer find their usual view. The board may have been a shared entry point, even if its issues remain. Tell affected people which project or alternative board to use.
- A saved filter remains after the board disappears. Board and filter removal are separate tasks. Review the filter’s ownership and dependencies before deciding whether it should also be removed.
- You are unsure whether issues were deleted. Search the relevant project or open another view that includes those issues. A missing board link alone does not confirm that project work has been removed.
FAQs About Deleting a Jira Board
Does deleting a Jira board delete its issues?
Deleting a board generally removes the board view, not the project issues displayed on it. Those issues usually remain in their project and may be available through another board or project view. If work seems to have disappeared, check the project and issue search before taking further action.
Can I delete a Jira board I do not own?
That depends on your Jira permissions and the board’s access settings. If you cannot see a deletion option, you may not have the required board administration rights. Ask the board owner or a Jira administrator to confirm who can remove it. Avoid using another person’s account or changing permissions without approval.
Will deleting a board also delete its saved filter?
Do not assume that the saved filter is removed with the board. The filter may have separate ownership and may still be used by another board, dashboard, or teammate. After removing the board, review the filter and its dependencies. Remove it only if it is no longer needed and you have permission.
Can a deleted Jira board be restored?
Whether a board can be recovered depends on your Jira product, version, and administrative options. Before confirming deletion, record the board’s name and review its filter and settings. If you have already deleted it, contact your Jira administrator promptly and ask whether recovery is available in your environment.
Conclusion
Deleting a Jira board is usually a short process, but checking its owner, users, and connected filter first can prevent avoidable confusion. Confirm the board name, use the available delete action, and verify that project issues remain accessible afterward.
If the board is no longer useful, removing it can make your workspace easier to navigate. If your team still needs its view, consider keeping it and clarifying ownership instead. A careful check before deletion gives you a cleaner Jira workspace without disrupting the work behind the board.