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

            [JSWSERVER-6706] Deletion of the Filter Associated with a Board Removes the Board

            Maria Marzec added a comment - - edited
            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 screenshot added to the ticket) 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

            Maria Marzec added a comment - - edited 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 screenshot added to the ticket) 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

            Andrew Fowler added a comment -

            In agreement here, this needs fixing as it is far too easy for users to accidentally delete filters associated to boards.

            Andrew Fowler added a comment - In agreement here, this needs fixing as it is far too easy for users to accidentally delete filters associated to boards.

            Gregory Miklos added a comment -

            Please fix this issue at your earliest convenience 

            Gregory Miklos added a comment - Please fix this issue at your earliest convenience 

            Keith added a comment -

            Are we allowed to ask what is taking so long to fix this?
            Seems like a very simple fix to add to the startup procedure.
            We have made scripts to address this but rather have this landmine resolved in the core product.

            Disappointing to be prepping for 9 LTS upgrade to see this still lingering

            Keith added a comment - Are we allowed to ask what is taking so long to fix this? Seems like a very simple fix to add to the startup procedure. We have made scripts to address this but rather have this landmine resolved in the core product. Disappointing to be prepping for 9 LTS upgrade to see this still lingering

            Maria Marzec added a comment -
            Atlassian Update – 10 May 2023

            Hi everyone,

            Thank you for taking the time to file and comment on this issue. We've reviewed it and agreed it’s a high priority for us to resolve. Our engineers have already started working on the issue.

            Please continue watching this ticket for future updates and changes in the timeline that may impact your work.

            Best regards

            Maria Mikołajczak
            Software Engineer

            Maria Marzec added a comment - Atlassian Update – 10 May 2023 Hi everyone, Thank you for taking the time to file and comment on this issue. We've reviewed it and agreed it’s a high priority for us to resolve. Our engineers have already started working on the issue. Please continue watching this ticket for future updates and changes in the timeline that may impact your work. Best regards Maria Mikołajczak Software Engineer

            Peter-Dave Sheehan added a comment -

            I found this page that seems to work: https://confluence.atlassian.com/jirakb/jira-software-boards-not-visible-after-filter-deletion-779158656.html

            Peter-Dave Sheehan added a comment - I found this page that seems to work: https://confluence.atlassian.com/jirakb/jira-software-boards-not-visible-after-filter-deletion-779158656.html

            Kent Rogers added a comment -

            The link posted in the previous comment and in the Current Status field doesn't appear to be visible. Even though I'm logged into my Atlassian account, I'm simply re-directed to: https://confluence.atlassian.com/alldoc/atlassian-documentation-32243719.html. Should it be visible?

            Kent Rogers added a comment - The link posted in the previous comment and in the Current Status field doesn't appear to be visible. Even though I'm logged into my Atlassian account, I'm simply re-directed to: https://confluence.atlassian.com/alldoc/atlassian-documentation-32243719.html . Should it be visible?

            Stasiu added a comment -
            Atlassian Update – 25 April 2023

            Dear Customers,

            Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog.

            The workaround for this bug is as follow:
            https://confluence.atlassian.com/display/GHKB/Boards+Are+Not+Visible+After+the+Filter+is+Deleted

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Best regards

            Daniel Dudziak
            Senior Software Engineer

            Stasiu added a comment - Atlassian Update – 25 April 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog. The workaround for this bug is as follow: https://confluence.atlassian.com/display/GHKB/Boards+Are+Not+Visible+After+the+Filter+is+Deleted Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Daniel Dudziak Senior Software Engineer

            Mia Perron added a comment -

            Throwing my hat in the "Please fix this" ring. This just bit my team, and there was NO warning when we deleted the filter that a Board would be affected. This is such a pain. Also, TY to alex779065377 for the lifesaver!

            Mia Perron added a comment - Throwing my hat in the "Please fix this" ring. This just bit my team, and there was NO warning when we deleted the filter that a Board would be affected. This is such a pain. Also, TY to alex779065377 for the lifesaver!

            Peter Christopher added a comment -

            I just ran into this issue. Since the affected board was being used as an issue source in a Jira Portfolio Plan, it has broken that too. The symptom is if you go to the Plan --> Configure --> Issue Sources, that page will sit on a progress bar and never load. You should consider not allowing the deletion of a filter that is being used on a board or anywhere else. Force the board to be deleted/updated first before allowing the filter deletion!

            Peter Christopher added a comment - I just ran into this issue. Since the affected board was being used as an issue source in a Jira Portfolio Plan, it has broken that too. The symptom is if you go to the Plan --> Configure --> Issue Sources, that page will sit on a progress bar and never load. You should consider not allowing the deletion of a filter that is being used on a board or anywhere else. Force the board to be deleted/updated first before allowing the filter deletion!

              255109c6c964 Maria Marzec
              rpillai RenjithA
              Affected customers:
              402 This affects my team
              Watchers:
              270 Start watching this issue

                Created:
                Updated:
                Resolved: