How to Delete a Board in Jira: A Clear Step-by-Step Guide
Want to clear Jira clutter without losing issues? Learn how to delete a board in Jira safely. Read now to check permissions and protect your work.
If a Jira board is cluttering your workspace, deleting the wrong item can create a bigger problem than the clutter. A board is a view of work, while a Jira project holds the work itself, and the two are easy to confuse when you are cleaning up. The wrong click could remove a useful view or leave teammates unsure where to find their issues. But here's the truth: deleting a board usually removes the board, not the Jira issues displayed on it. You can reduce the risk by checking the board name, confirming your permissions, and reviewing its saved filter before you delete anything. Here’s a clear walkthrough, plus a few checks to help you clean up safely.
How to delete a board in Jira
In Jira Cloud, open the board list, find the board, and choose its delete option. You generally need board administration rights to remove it. Deleting the board does not delete the issues shown on it.
Confirm which board you want to remove. Open the board and check its name, project context, and issue view. If teammates rely on it for a sprint or work queue, let them know before proceeding.
Check your permissions. Board deletion is typically limited to the board administrator. If the delete option is missing, ask the board admin or a Jira administrator to confirm your access.
Open the board directory. In Jira Cloud, select Boards and then View all boards. Depending on your navigation layout, you may find the board list under Your work or a similar menu.
Find the board and open its actions. Locate the intended board, then select the three-dot menu or More option beside its name.
Choose Delete and review the confirmation. Read the warning carefully. Confirm only when the board name matches the one you intend to remove.
Verify the result. Return to the board list and check that the board no longer appears. If related issues still matter, open their project or another board to confirm they remain available.
Jira navigation can vary by product version and organization settings. If you use Jira Data Center or an older interface, look for the board directory and its board actions; an administrator may need to help if the menu differs.
What to check before you remove a board
Before deletion, check whether the board is active, who uses it, and whether another workflow depends on it. A Scrum board may support a current sprint, while a Kanban board might be a team’s daily work queue.
Here's why: Jira boards can use saved filters to decide which issues appear. A filter may be shared with other boards or people, so review its use before changing or removing it. If the filter supports another view, keeping it intact can prevent an avoidable interruption.
Ask the board administrator whether the board is still in use.
Check for active sprints, team dashboards, or links that point to the board.
Identify whether the saved filter is used elsewhere.
Record the board name and important settings if your team may need to recreate it.
For example, a product team might retire an old release board while keeping its saved filter for a reporting view. Removing the board and deleting the filter are separate actions, so treat them separately.
Board, project, and filter: know what each one does
A Jira board organizes and displays issues that match its configuration. A Jira project contains the issues and related project settings. A saved filter defines which issues a board can display.
Let me explain with a simple example: a team may use one project for customer requests and create separate boards for urgent work and planned work. Deleting one board should not remove the project’s issues or automatically erase the other board.
Board: A view for tracking work, such as a sprint or Kanban board.
Project: A Jira area where a team organizes issues and project activity.
Saved filter: A set of criteria that selects which issues appear in a board or other view.
You might be wondering: what if you want to remove the project too? That is a different administrative action with wider consequences. Confirm the project name and impact separately before asking an administrator to delete it.
What happens after a board is deleted?
The board should disappear from the board directory, while the Jira issues it displayed remain in their project. The issues can still be reached through another board, project view, search, or saved filter when you have access.
The board’s configuration is no longer available as a working board after deletion. If the team later needs the same view, an administrator may have to create a replacement and configure its filter, columns, and other settings again.
The best part? You can often preserve the team’s work without preserving an outdated board. For instance, a team can retire a duplicate board while keeping the project and its active issues untouched.
Jira’s exact behavior and available recovery options can depend on the deployment and permissions. If the board was removed by mistake, contact a Jira administrator promptly and ask whether it can be restored or recreated.
Safer alternatives to deleting a board
Deletion makes sense when a board is obsolete, duplicated, or tied to a workflow that has ended. If you are unsure, a reversible cleanup step can give you time to confirm the impact.
Rename it clearly. Add a label such as “Retired” or “Do not use” so teammates recognize its status.
Review access and sharing. Limit who can use or edit the board where your Jira setup allows it.
Update the saved filter carefully. First check whether other boards or reports rely on it.
Ask the team before removal. A short announcement can reveal a hidden dependency, such as a dashboard link.
For example, if a board has not been used since a completed launch, label it as retired for a short review period. If nobody reports a need for it, deletion is easier to approve with confidence.
Board management solution: ONES.com
Value proposition
ONES.com brings project management and knowledge management together in a unified platform powered by ONES Assistant. ONES Project is the project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.
Core capabilities
Pain: Teams lose time switching between project views. ONES capability: ONES Project provides project management with sprint management and Jira-compatible workflows. Result: Teams can plan and track work in a familiar structure.
Pain: A rigid workflow may not match a team’s approval process. ONES capability: Custom workflows and fields let teams shape how work moves. Result: The board and workflow can reflect practical team needs.
Pain: Manual status changes create repetitive work. ONES capability: Automation supports routine workflow actions. Result: Teams can reduce recurring administrative steps.
Pain: Project progress is hard to review consistently. ONES capability: Built-in reporting gives teams reporting features within the platform. Result: Project leads can review progress without relying on extra plugins for every reporting need.
Pain: Plugin-heavy setups can add maintenance overhead. ONES capability: Native project management capabilities cover workflows, fields, sprint management, automation, and reporting. Result: Teams can reduce dependence on separate plugins where native features meet their needs.
Pain: Some organizations require control over deployment. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can choose an environment aligned with their operational requirements.
Pain: A self-hosted setup may seem limited compared with cloud. ONES capability: The cloud and self-hosted versions have full feature parity. Result: Deployment choice does not require giving up feature access.
Pain: Teams need to evaluate a platform before committing broadly. ONES capability: The free plan supports up to 30 seats. Result: A team can explore the project management workflow with a limited group.
Application scenarios
Teams moving from Jira: A team that wants Jira-compatible workflows can assess ONES Project as a Jira alternative. It can map existing sprint routines and custom fields while reviewing which plugins remain necessary.
Organizations with deployment constraints: A company requiring an on-premise, private cloud, or air-gapped environment can evaluate the matching ONES.com deployment. Full feature parity across cloud and self-hosted versions helps keep capability decisions separate from hosting choices.
Teams connecting project work and knowledge: A group can use ONES Project for project management and consider ONES Wiki for knowledge management. Because they are sold separately, the team can choose the product that fits its need.
Common challenges when deleting Jira boards
The delete option is missing
Problem: You can open the board but cannot find a delete action. Solution: Check whether you are listed as a board administrator. If you are not, contact the board admin or Jira administrator to request removal.
The wrong board may be selected
Problem: Several boards have similar names, making the target unclear. Solution: Open the board and confirm its team, project context, and purpose before using its action menu.
A filter may be shared with another view
Problem: The board’s saved filter may also support another board or report. Solution: Review the filter’s sharing and use before making separate filter changes. Delete only the board if that is the intended cleanup.
Teammates still use the board
Problem: A board looks inactive but remains linked in team routines or dashboards. Solution: Announce the planned removal and offer a replacement view. A brief check with the team can uncover dependencies before they interrupt work.
FAQs
Does deleting a Jira board delete its issues?
No. A Jira board is a way to view and organize issues; it is not the project that holds them. Removing a board should leave its issues in their Jira project. You can still reach those issues through another board or project view if your permissions allow it. Confirm that the selected action says you are deleting a board, especially if you also manage projects.
Can I delete a Jira board if I am not its administrator?
Usually, board administration permissions are required to delete a board. If you cannot see the delete action, ask the board administrator or a Jira administrator to check your access. Avoid changing permissions or filters just to make the option appear, since those settings may affect other people or views.
Will deleting a board also remove its saved filter?
Board deletion and filter management are separate actions. A saved filter may be shared with other boards, reports, or teammates, so check its use before changing it. If the filter still supports another view, keeping it can prevent that view from breaking. Review Jira’s confirmation and filter settings in your organization before taking additional cleanup steps.
Can I recover a board after deleting it?
Recovery options can vary by Jira version, configuration, and permissions. Contact your Jira administrator as soon as possible and provide the board name and approximate deletion time. If restoration is unavailable, the administrator may be able to recreate the board using its former filter and settings, if those details are still available.
What should I do if I want to delete a Jira project instead?
Project deletion is different from board deletion and can affect the project’s issues and related work. Confirm the project name, ownership, and impact before proceeding. If you only want to remove a team’s view, delete the board instead. Ask a Jira administrator to review project deletion requirements and any retention rules that apply.
Conclusion
Deleting a Jira board is a short process: confirm the board, check your permissions, open the board directory, and use its delete action. The main safeguard is knowing that a board, its saved filter, and its project are distinct parts of Jira.
Before you confirm, check team dependencies and filter use. If the board is only temporarily unwanted, rename or retire it first. A careful review helps you clear clutter while keeping the issues and views your team still needs.