How to Delete a Board in Jira: A Step-by-Step Guide (2026)
Worried deleting a board in Jira will erase your work? Follow safe steps to remove the board without losing issues. Read now to learn how.
Deleting the wrong Jira board can disrupt a team’s daily workflow, especially when several boards show the same project work. The board may look like the project itself, so it’s easy to worry that removing it will erase issues, sprints, or team history.
But here's the truth: deleting a board generally removes that board view, not the Jira issues it displays. The real risk is losing a useful setup, such as a filter, swimlane arrangement, or quick way to track work.
Before you delete anything, check the board name, its owner, and the saved filter it uses. Then follow the steps below to remove the intended board and verify that the underlying work remains available. If the interface looks different in your Jira instance, use the board’s administration options or ask a Jira administrator for help.
How to Delete a Board in Jira Safely
In Jira Cloud, you can usually delete a board through the board directory. You’ll need the appropriate board administration permission, and the exact labels may vary slightly across Jira versions.
Confirm which board you’re removing. Open the board and check its name, project, and contents. If the board is used by several teams, ask its owner before proceeding.
Check the board’s filter and setup. Review the saved filter, columns, swimlanes, and quick filters. Record any settings your team may need to recreate.
Open the board directory. In Jira, select Boards, then choose View all boards. Depending on your Jira interface, the directory may appear under a similar boards menu.
Open the board’s actions menu. Find the correct board and select its three-dot menu or other actions control. Double-check the board name before continuing.
Choose Delete and confirm. Review Jira’s confirmation prompt, then proceed only if you’re sure the board is no longer needed. If you can’t see the option, you may not have board administrator permission.
Verify the result. Return to the board directory and confirm the board no longer appears. Open the project or another board to check that the issues your team needs are still accessible.
Deleting a board typically removes its view, rather than the Jira project or issues shown on it. Treat its saved filter as a separate item: check whether it still exists, who can access it, and whether anyone depends on it before making further changes.

What to Check Before Removing a Board
Start by finding out who uses the board. A team might not open it every day, yet still rely on it for sprint planning, release tracking, or a weekly review. Ask the board owner and any teams whose work appears there.
Next, inspect the filter and configuration. For example, a board might display issues from several projects because its filter includes multiple project keys. Deleting that board can remove a convenient view even though those issues remain in Jira.
Here's why: a board is a way to organize and display work, while projects and issues hold the work itself. Checking both the board and its associated settings helps you avoid disrupting a workflow by mistake.
What Happens to Issues, Filters, and Sprints?
Deleting a board generally does not delete the issues it displayed. Those issues remain in their Jira projects and can still be reached through project views, search, or another board with a suitable filter.
Filters deserve a separate check. A board can use a saved filter, and that filter may be useful to another board or person. After board removal, verify whether it remains available and whether its sharing permissions still make sense.
For example, if a release board displays issues from two projects, those issues should remain in their projects after the board is removed. The team may still need to recreate the board or find another view for release planning.
How to Handle Missing Delete Options
If the actions menu doesn’t show a delete option, check whether you’re signed in with the account that administers the board. Board permissions and Jira administration permissions are different, so access to a project alone may not be enough.
Ask the board owner or a Jira administrator to confirm who can manage it. If the owner has left the team, an administrator may need to review ownership and access before anyone can remove the board.
You might be wondering: should you delete the board if you’re unsure? Pause and ask for confirmation. Renaming it temporarily or documenting its settings for the team can give you time to verify that nobody still relies on it.
Alternatives to Deleting a Jira Board
Sometimes the board is still useful, but its current setup no longer fits the team. You could update its filter, rename it to clarify its purpose, or adjust columns and quick filters so people can find the right work more easily.
If two boards serve nearly the same purpose, compare their filters and configurations before deciding whether to consolidate. For instance, a team may keep one board for active sprint work and another for cross-project planning because each supports a different meeting.
The best part? You don’t have to remove a board just because it looks cluttered. A small change to its name or filter may solve the problem while preserving a familiar workflow.
A Project Workflow Alternative: ONES.com
When teams repeatedly create, revise, or retire boards to keep work visible, it may help to review the project workflow itself. ONES.com combines project management and knowledge management in one platform; ONES Project is its project management product and a Jira alternative. ONES Project and ONES Wiki are sold separately.

For a team considering a different setup, the practical question is whether it can retain familiar project controls while reducing the need to assemble workflows through extra plugins. ONES Project supports Jira-compatible workflows, custom fields, sprint management, automation, and built-in reporting. It also offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.
Core Capabilities
Board confusion: Jira-compatible workflows let teams use familiar ways to organize project work, helping reduce disruption during a transition.
Repeated manual steps: Automation can handle routine workflow actions, reducing repetitive work for project teams.
Limited sprint visibility: Sprint management gives teams a structured way to plan and follow sprint work.
Inflexible issue details: Custom fields let a team capture information that matters to its process, so people can track work with fewer workarounds.
Scattered progress updates: Built-in reporting helps teams review project progress without relying on a collection of separate reporting add-ons.
Plugin-heavy setups: Native project capabilities can reduce dependence on extra plugins for common workflow needs.
Restricted hosting requirements: On-Premise, Private Cloud, and Air-gapped deployments offer options for teams that need self-hosted environments.
Uncertain team fit: The free plan supports up to 30 seats, giving a smaller team room to evaluate its project workflow.
Application Scenarios
A software team that keeps creating boards for different sprint views could assess whether a consistent workflow, custom fields, and sprint management would make its work easier to follow. The goal is to choose a structure that fits the team, rather than repeatedly rebuilding views.
A company with restricted network requirements could evaluate ONES Project’s self-hosted deployment options. It can compare the required hosting approach and workflow needs before deciding whether a Jira alternative fits its environment.
ONES.com is worth considering when a team is reviewing its project management approach, rather than simply looking for a way to delete one board. The right choice depends on the team’s workflows, hosting needs, and appetite for changing platforms.
Common Challenges When Deleting a Jira Board
The wrong board gets selected. Several boards may have similar names. Compare the board name, project, and filter before using its actions menu.
The team loses a familiar view. Issues may remain, but people can still lose a useful way to organize them. Ask regular board users whether another view meets their needs.
The delete option is missing. Your account may lack board administration permission. Contact the board owner or Jira administrator instead of trying to work around access controls.
A saved filter remains after board removal. Check the filter separately and confirm whether anyone still uses or needs access to it before changing its settings.
Frequently Asked Questions
Does deleting a Jira board delete its issues?
Usually, deleting a board removes the board view rather than the issues displayed on it. The issues remain in their Jira projects and may still appear in other views. Before you proceed, check that you’re removing a board and not taking a separate action on a project or issue. Afterward, open the relevant project or another board to confirm your team can still find its work.
Can I delete a board if I didn’t create it?
It depends on your permissions and how the board is managed. Being able to view a board, or work in its project, doesn’t necessarily give you permission to delete it. Check whether you have board administrator access. If the delete action is missing, contact the board owner or a Jira administrator to confirm who can manage the board.
Will the board’s saved filter disappear too?
Don’t assume the filter will be removed when you delete a board. A saved filter can be managed separately and may still be used by another board or shared with other people. Check the filter after the board is removed, and review its owner and sharing permissions. If nobody needs it, ask an administrator or the filter owner about the appropriate cleanup.
Can I recover a deleted Jira board?
Recovery options can depend on your Jira version, permissions, and the board’s configuration. Before deleting, note the board’s filter and important settings so the team has a reference if it needs to recreate a similar view. If the board has already been deleted, contact a Jira administrator promptly and explain what was removed. They can check which recovery or recreation options are available in your environment.
Conclusion
To delete a Jira board, confirm the exact board, review its users and filter, then remove it through the board directory if you have the required permission. Verify afterward that the board is gone and the underlying project work remains accessible.
A quick check can prevent a small cleanup task from interrupting sprint planning or team reporting. If you find that boards keep multiplying because the workflow is hard to manage, review the process and consider whether a different project management setup would suit your team better.