Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-6706

Deletion of the Filter Associated with a Board Removes the Board

XMLWordPrintable

    • 6
    • 84
    • Severity 2 - Major
    • 357
    • 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

      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:

      1. Create a rapid board
      2. Delete the filter associated with the board from JIRA
      3. The board disappears from the Agile Menu and Manage Boards page.

      Expected Results:

      1. 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:

      1. 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

      Workaround

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

        1. filter_deletion_warning_plugin.png
          36 kB
        2. filter-delete-warning.png
          61 kB
        3. filter-deletion-new-warning.png
          filter-deletion-new-warning.png
          39 kB

              255109c6c964 Maria Marzec
              rpillai RenjithA
              Votes:
              402 Vote for this issue
              Watchers:
              270 Start watching this issue

                Created:
                Updated:
                Resolved: