Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: Highest
Fix Version/s: 9.11.0
Affects Version/s: 6.0.7, 6.6.80, 7.0.0, 6.7.12, 7.1.9, 8.20.10, 9.4.6
Component/s: Board configuration
Labels:
- Triaged
- affects-cloud
- affects-server
- banshee
- fixme
- flash
- lts-backport
- pse-request
- st10
- sw-c
- triaged

Introduced in Version:
6
Support reference count:
84
Symptom Severity:
Severity 2 - Major
UIS:
357
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:

Hide

Atlassian Update – 11 Aug 2023

Thank you for reporting this issue. In the last weeks we have been working hard on fixing it.

Summary of the problem:

When deleting a filter, there wasn’t any extra check to confirm if any associated boards existed. This led to the potential deletion of a filter even if there were boards linked to it. Although the boards remained within the Jira system, they didn’t display correctly since the filter responsible for collecting the issues was removed. This situation could result in significant data loss and an increased load on the system due to the presence of unusable boards in the database.

New behaviour after the change:

Our solution introduces a different user experience during the process of filter deletion. Now, when attempting to delete a filter through the Manage Filters page, users will encounter a warning (please refer to the provided screenshots) informing them that the filter cannot be deleted along with the list of the associated boards. The deletion of the filter will only be possible after all associated boards presented in the warning have been deleted first. This adjustment serves to minimize the risk of accidental data loss and provides a clearer user experience. Please, note that those changes were not introduced to the REST API responsible for filter deletion.

Status of the fix and Fix Version:

We’re pleased to inform you that the solution is fully prepared, and we’re in the process of marking this ticket as “Waiting for Release” with Fix Version 9.11.0.

Please be aware that this solution cannot be applied to previous versions due to significant changes, including the introduction of a new API. To benefit from this update, it will be necessary to upgrade Jira to the latest feature version.

We appreciate your patience and understanding as we work to enhance your experience with our product.

Best regards

Maria Mikołajczak
Software Engineer

Show
Atlassian Update – 11 Aug 2023 Thank you for reporting this issue. In the last weeks we have been working hard on fixing it. Summary of the problem: When deleting a filter, there wasn’t any extra check to confirm if any associated boards existed. This led to the potential deletion of a filter even if there were boards linked to it. Although the boards remained within the Jira system, they didn’t display correctly since the filter responsible for collecting the issues was removed. This situation could result in significant data loss and an increased load on the system due to the presence of unusable boards in the database. New behaviour after the change: Our solution introduces a different user experience during the process of filter deletion. Now, when attempting to delete a filter through the Manage Filters page, users will encounter a warning (please refer to the provided screenshots) informing them that the filter cannot be deleted along with the list of the associated boards. The deletion of the filter will only be possible after all associated boards presented in the warning have been deleted first. This adjustment serves to minimize the risk of accidental data loss and provides a clearer user experience. Please, note that those changes were not introduced to the REST API responsible for filter deletion. Status of the fix and Fix Version: We’re pleased to inform you that the solution is fully prepared, and we’re in the process of marking this ticket as “Waiting for Release” with Fix Version 9.11.0 . Please be aware that this solution cannot be applied to previous versions due to significant changes, including the introduction of a new API. To benefit from this update, it will be necessary to upgrade Jira to the latest feature version. We appreciate your patience and understanding as we work to enhance your experience with our product. Best regards Maria Mikołajczak Software Engineer

Description

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:

Notes:

At the same time the board related data is still available in the database.

Workaround

Workaround

Refer the article - https://confluence.atlassian.com/display/GHKB/Boards+Are+Not+Visible+After+the+Filter+is+Deleted

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

filter_deletion_warning_plugin.png
36 kB
25/May/2016 12:58 AM
filter-delete-warning.png
61 kB
24/May/2016 10:57 PM
filter-deletion-new-warning.png
39 kB
11/Aug/2023 6:50 AM

Issue Links

causes

JPOSERVER-3142 Issue source page loads indefinitely when the plan is associated with a board with no filter

Closed

JSWSERVER-10613 As an Admin I want the Sprint Marker Migration to check for orphaned boards

Closed

duplicates

JSWSERVER-12069 Deleting filter = scrum board vanishes! ... Surely not?

Closed

is duplicated by

JSWSERVER-8313 Deleting a filter associated with a board, deletes a board with no warning

Closed

JSWSERVER-12125 Warn when deleting a Saved Filter if Agile boards are using it

Closed

JRASERVER-31465 deleting JIRA filter/project may break greenhopper boards

Gathering Interest

is related to

JRACLOUD-31465 Deleting JIRA filter/project may break greenhopper boards

Closed

JRASERVER-25955 Plugin Point for Saved Filters

Closed

JSWSERVER-11827 In copying Agile Board, it doesn't create a copy of the associated Filter

Closed

relates to

JSWSERVER-24979 No warning when deleting filter used in as issue source in plan

Gathering Impact

JSWSERVER-7063 As a user, I don't want the board's filter to be deleted from JIRA which can cause the board to be vanish

Closed

JSWSERVER-12568 Deleting filter should prompt a warning message if filter is associated with any board

Closed

SW-121 Loading...

SW-6892 Loading...

BJBR-22 Loading...

MLP-475 Loading...

MNSTR-3799 Loading...

was cloned as

JSWCLOUD-6706 Deletion of the Filter Associated with a Board Removes the Board

Closed

is cloned by: SONIC-198 Loading...

Mentioned in

CSS Top Asks - Jira On Prem: JSWSERVER-6706 | Deletion of the Filter Associated with a Board Removes the Board

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 is duplicated by, 3 is related to, 8 relates to, 1 was cloned as, 1 is cloned by, 1 Mentioned in, 60 mentioned in)

Activity

People

Assignee:: Maria Mikołajczak

Reporter:: RenjithA

Votes:: 402 Vote for this issue

Watchers:: 271 Start watching this issue

Dates

Created:: 21/Nov/2012 2:13 AM

Updated:: 2 days ago 6:41 PM

Resolved:: 30/Aug/2023 2:48 PM

Details

Summary of the problem:

New behaviour after the change:

Status of the fix and Fix Version:

Description

Summary:

Steps to Reproduce:

Expected Results:

Actual Results:

Regression:

Notes:

Workaround

Attachments

Attachments

Issue Links

Activity

People

Dates