I like the scary Active Sprint delete warning. I can show folks how dangerous it is to create a board without the Admin.
I’ve been using an odd workaround for deleting a 2nd board with an active Sprint on the 1st board.
Just change the board’s query.
Usually the Filter Query is like:
project = MyProject ORDER BY Rank ASC
Change it with
Board Settings -> General and filter -> Filter -> Edit Filter Query
project = MyProject AND text ~ "DeleteMyBoardRandomText" ORDER BY Rank ASC
The board will be empty, now you can delete it. It’s worked so far, maybe I’ve been lucky?
The precise steps will depend on whether you are on server or cloud. However, you must own the board you want to delete or be a system admin. Navigate to the the view all boards screen (cloud click magnifying glass and boards) then find board and click on ellipses on right.
When I try to delete a board, I get a warning that this board contains and active sprint and that I might lose work. This goes against everything I thought a JIRA board was. I thought the board was just a view of the project. I created a bunch of boards to experiment and now it looks like I can't get rid of these. Any way I can delete the boards without affecting the project or the sprints?
Your understanding of boards is mostly incorrect.
A board is a view of a set of issues, not a project. That set of issues might well be as simple as "everything in project X", but often it's not - many boards cover several projects, or sub-sets of projects.
A sprint belongs to a board effectively. The board you are trying to delete must have been used, with one or more sprints created. You'll need to think about whether that is ok to throw away.
However, I come back to the "board is a view of issues" - deleting a board will only change one thing on the issues it includes - it will remove the sprint(s) the issue is in (no board = no sprint, so the issue can't be in the sprint any more). It will NOT touch any other data on the issue. So, if you look at the sprints for the board, decide you don't need them, it's perfectly safe to remove the board and its sprints.
Hi Nic, Thanks for clarifying that.
However, when I try to delete a board which I created "based on existing project", it is saying I will lose the active sprint which was on the original board (same sprint name). I didn't create a new sprint on the new board. So you can understand why I am reluctant to delete. I am completely fine to lose the sprint on the board I am trying to delete but I am worried I will also lose the sprint in the original board since the warning names the same sprint name.
Hi, I was just having the same dilemma. However, when I go to the "view all boards" and click delete on the unwanted one, the warning about the active sprints pops up but the delete button is grayed out. It looks like it actually wants me to close or delete the 2 sprints that are active on the unwanted board. Note- they are the same active sprints as 2 other projects so I can't close them yet. Were you able to close the sprints without closing them on your other projects? @Eshan Salpadoru
@Marco Martinez, welcome to the Community! First, as a matter of Community process, it is generally best to start a new question if the question isn't directly associated w/ the current thread. With that said...
What do you mean by "deleting it", that is, what does the "it" refer to? The board or the project?
If you no longer want the board then you simply delete it. Doing so will not impact the project or an issues. You can't remove a kanban from a project and still have it exist unless of course the Kanban is associated w/ multiple projects. In which case you could remove one of the projects in the board filter and leave the other project(s) and the kanban will remain.
Now maybe you are actually wanting the board to be represented by something different that it currently is? This can be done by editing the boards filter.
All of the above can only be done if you own the board or are a system admin.
If this hasn't cleared up your question I would suggest opening a new question.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs