-
Bug
-
Resolution: Fixed
-
Highest
Summary:
Deletion of a filter that is associated with a Rapidboard causes the Rapidboard to disappear from the Agile menu as well as the Manage boards.
Steps to Reproduce:
- Create a rapid board
- Delete the filter associated with the board from JIRA
- The board disappears from the Agile Menu and Manage Boards page.
Expected Results:
- The board should be still be present in Manage boards and when GH detects that it is not having the associated filter, it should request the owner of the board to re-associate it with a filter or with project(s)
Actual Results:
- The board disappears from the Agile Menu and Manage Boards page.
Regression:
NA
Notes:
At the same time the board related data is still available in the database.
Workaround
- causes
-
JSWCLOUD-10613 As an Admin I want the Sprint Marker Migration to check for orphaned boards
- Closed
- duplicates
-
-
- Closed
-
- is cloned from
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
- relates to
-
- Closed
-
- Closed
- was cloned as
-
SW-6892 Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWCLOUD-6706] Deletion of the Filter Associated with a Board Removes the Board
I just shot myself in the foot by deleting the filter that drives a board. Some warning came up, that I clicked through. Now the board has been deleted. Ugh! This should not be permitted!
Warning isnt enough. The board has more details than just a filter. Sprints associated with it are also important.
To solve this problem we've created a feature that alerts you to the fact that the filter you're trying to delete is currently being used by other boards, and therefore cannot be deleted until its association to those boards is removed.
It is a very nice looking warning, but... You know people don't read these messages, right? They just click through the message, and then complain about the missing board.
Wouldn't it just be easier to disallow this action? You could use your lovely message box to simply tell them that the filter can't be deleted because it is used in Board X, and then you only need a single OK button.
Think of all the support requests and complaints you could save not only for your customers, but for YOURSELF, by simply enforcing that boards must be deleted first 
NB: The proposed workaround (https://confluence.atlassian.com/display/GHKB/Boards+Are+Not+Visible+After+the+Filter+is+Deleted) only applies to the on-premise install; not the Cloud version.
Is there any workaround available for the Cloud version?
Thanks in advance.
Thorsten Habich
added a comment - Is there already a estimation when this issue will be fixed? Great! An inconsistency of one of the most used objects (rapid / agile board) is sleeping in the backlog. Do you guys just sense how many users curse on that behaviour? The warning is fine on one end but the major point is that the board is not editable / usable anymore.
Given that a board is holding more information than just a filter ID it is unacceptable that you won't fix this bug as soon as possible. As an administrator I need to restart my instance to make a board available again.
Please implement this in the JIRA Cloud version. A project lead deleted one of his filters that he forgot was linked to a board. So we had to recreate the filter and board and re-setup the Quick Filters, Card Colors, Card Layout, Estimation, and Issue Detail. This would have been avoided if he could have received a Warning message before deleting the filter.
piyush_annadate - the warning is part of JIRA Software from 7.1.1 Server, it's not a plugin as such.
Kind regards,
Martin
JIRA Software
used the priortization filter and the issue ub the backlog, I can not see the stories by epic. I mean with out this filter im able to click on epic in baclog and can see the stories unser that perticlular epic but after using the priortizing filter im not able to do the same. I tried to delete the filter and get back to the orignal view but it says you need to deassociate the filter first and wow THERE IS NO OPTION TO DEASSOCIATE THAT FILTER from the board.