How to Delete a Jira Board: Steps, Checks, and Tips in 2026
Need to delete a Jira board without losing work? Learn the key checks and steps to delete a Jira board safely. Read now before you remove it.
A Jira board can outlive the project or workflow it was created to support. Removing the wrong one, though, can leave teammates without familiar views, sprint reports, or useful links. The uncertainty is frustrating: will deleting a board erase issues, filters, or project work too?
But here's the truth: deleting a Jira board removes the board, not the issues it displays. Before you act, check which board you have, who relies on it, and whether its saved filter is still useful. I’ll walk you through the deletion steps, the checks that prevent surprises, and what to do if the delete option is missing. You’ll also learn how to distinguish a board from a project, filter, or sprint, so you can remove the right thing with confidence.
How to delete a Jira board safely
First, confirm the board is no longer needed. Then remove it through Jira’s board menu or board directory, depending on your interface and permissions.
- Identify the exact board. Open it and check its name, project context, board type, and displayed issues. If several boards have similar names, ask the team which one they use.
- Check the board’s filter. Open the board settings and review its saved filter. The filter determines which issues appear, and it may support other boards or reports.
- Check dependencies. Ask teammates whether they rely on the board for sprint planning, Kanban tracking, reports, or shared links. Save any important URLs and details you may need later.
- Confirm your access. If Jira does not show a delete option, you may lack board administration rights. Ask a board administrator or Jira administrator to confirm who can remove it.
- Open the board’s actions. In Jira Cloud, look for the board’s ellipsis menu in the board directory or its board menu. Interface labels and locations can vary by Jira version.
- Select Delete board. Read the confirmation carefully and verify the board name before confirming. If the prompt names a different board, cancel and check your selection.
- Verify the result. Return to the board directory and check that the intended board no longer appears. Confirm that the project and its issues are still available.
For example, if a team has an active Scrum board and an abandoned Kanban board, compare their names and filters before deleting either one. That small check can prevent a needless interruption.

What to check before removing a board
Confirm you are deleting a board, not a project
A board is a view of issues, while a project organizes work and permissions. Removing a board is not the same action as deleting a project.
Look at the board name and project context before proceeding. If you intend to retire an entire project, stop and follow your organization’s project removal process instead.
Review the saved filter and its sharing
A board’s saved filter controls which issues appear. Other boards or teammates may rely on that filter, even if they rarely open the board you plan to delete.
Check the filter’s name, owner, and sharing settings. If it remains useful, keep it. If nobody needs it, handle its removal separately and only after checking its dependencies.
Ask about active work and reporting
A board may be part of a team’s daily routine even when its name looks outdated. Check whether anyone uses it to plan a sprint, review work, or open historical reports.
For instance, a team may have moved to a new board but still use the old one to review earlier sprint activity. Agree on an alternative before removing that familiar route.
What deleting a Jira board changes
Deleting a board removes that board from Jira. It does not, by itself, delete the underlying project or the issues shown on the board.
The saved filter is a separate item, so deleting a board does not necessarily remove its filter. Review it independently, especially when other people or boards may use it.
Board-related access paths can change, too. Teammates may lose a familiar way to view work, and links to the removed board may stop working. Before deletion, share the replacement board or project view with anyone who needs it.
Think of a board as a window onto work rather than the work itself. Removing one window does not remove the issues, but people may need another way to find them.
Cloud and self-managed Jira considerations
The exact menu can differ across Jira Cloud and self-managed Jira installations. Jira administrators may also adjust permissions or navigation, so the same action can appear in a different place.
Start in the board directory and inspect the board’s actions menu. If you cannot find a delete command, open the board settings or ask an administrator to confirm the available process.
Permissions matter. A board administrator may be able to manage a board, while a particular Jira setup may require administrator help for deletion. Avoid trying to work around a missing permission by deleting a related project or filter.
Solution for teams rethinking Jira boards: ONES.com
ONES.com combines project management and knowledge management in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

If your team is cleaning up boards because project workflows have become difficult to manage, consider whether a more unified setup would help. ONES.com supports Jira-compatible workflows, custom fields, sprint management, automation, and built-in reporting. Teams can use cloud or self-hosted deployments, including on-premise, private cloud, and air-gapped options.
Core capabilities
- Board sprawl → Custom workflows and fields in ONES Project → Shape work views around the team’s process instead of keeping redundant setups.
- Familiar Jira practices → Jira-compatible workflows → Keep established ways of working while evaluating a Jira alternative.
- Manual sprint coordination → Sprint management → Plan and track sprint work within the project management environment.
- Repeated routine actions → Automation → Reduce manual steps for recurring workflow tasks.
- Scattered progress visibility → Built-in reporting → Give teams a direct way to review project progress.
- Too many add-ons → Native feature parity between cloud and self-hosted versions → Reduce reliance on plugins while choosing a suitable deployment.
- Restricted network requirements → On-premise, private cloud, or air-gapped deployment → Match the hosting approach to organizational constraints.
- Disconnected project work and team knowledge → ONES Project and ONES Wiki, available separately → Choose either product or use both within the broader ONES.com platform.
Application scenarios
A team consolidating old boards: A product group can review its workflows and decide which views are still necessary. It can then assess whether ONES Project’s custom workflows, fields, and reporting fit its ongoing project needs.
An organization with deployment restrictions: A team that cannot use a public cloud service can evaluate ONES.com’s self-hosted choices, including on-premise and air-gapped deployment. It can consider project management without changing its network requirements.
Common challenges when deleting a board
- You cannot find the delete command. Check whether you have board administration rights. If the option remains unavailable, ask a Jira administrator to confirm the permissions and deletion process.
- You are unsure which board is obsolete. Compare board names, filters, project context, and recent team use. Ask the people who rely on it before making a final choice.
- Teammates still need the old view. Identify a replacement board or project view, then share its link before deletion. That gives the team a clear route to its work.
- You are concerned about losing issues. Remember that removing a board does not by itself delete its underlying issues. Confirm the project remains available after deletion.
- You may also want to remove the filter. Treat the saved filter as a separate item. Check its owner, sharing, and use before deciding whether it should remain.
Frequently asked questions
Does deleting a Jira board delete its issues?
No. Deleting a board removes the board view, not the issues displayed through it. Those issues remain in their project unless someone separately deletes them. After removing the board, teammates can still reach issues through other boards, project views, or Jira search. If you are retiring a project as well, treat that as a separate action and check your organization’s process first.
Does deleting a board also delete its saved filter?
Not necessarily. A board and its saved filter are separate Jira items. The filter may remain available after the board is removed, and other boards or people may rely on it. Review its owner and sharing before making a separate decision about the filter. Keeping a useful filter can preserve a way to find issues without keeping an obsolete board.
Why can’t I delete a Jira board?
You may not have permission to manage or delete that board, or your Jira interface may place the action elsewhere. Check the board’s settings and actions menu, then ask a board administrator or Jira administrator to review your access. Avoid removing the project or filter as a workaround. Those are separate items and may be used by other teams.
Can I recover a Jira board after deleting it?
Do not assume Jira provides a simple restore button for a deleted board. Before deletion, record the board’s filter details, settings, and any important links you may need to recreate its view. If you deleted it by mistake, contact your Jira administrator promptly. They can check which recovery options are available for your specific Jira setup.
Conclusion
Before you delete a Jira board, confirm its identity, check its saved filter, and ask whether teammates still need its views or reports. Then use the board’s delete action and verify that the project and issues remain accessible.
That short review helps prevent an avoidable disruption. If board cleanup points to a wider workflow problem, assess whether your team needs a different project management setup, such as ONES Project, rather than simply removing another view.