Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-26453

Quick filter results are not applied when switching between Active Sprint and backlog.

XMLWordPrintable

      Issue Summary

      When selecting any quick filter from the Active Sprint, and switching from Active sprint to the backlog section (or refreshing the page), the quick filter shows as selected however the results are not filtered.

      Steps to Reproduce

      1. Create a quick filter for the Active Sprint.
      2. Select the quick filter.
      3. Navigate to the Backlog of the same board.
      4. Navigate back to the Active Sprint.

      Expected Results

      Previous results from the selected quick filter should be visible in the backlog.

      Actual Results

      Results are not filtered, however, the quick filter is shown as selected.

      Workaround

      Unselect and select the quick filter again in the Active Sprint.

            [JSWCLOUD-26453] Quick filter results are not applied when switching between Active Sprint and backlog.

            Hannu Jalonen added a comment -

            Could you please fix this?

             

            There are several similar reports on the subject. At least the following issues:

            https://jira.atlassian.com/browse/JRACLOUD-86001
                => Created: 19/Jan/2023 1:15 PM
                => Votes: 11
                => Closed at 17.4.2024 with comment: "The behavior described appears to have been fixed at some point after this Feature request was raised:"
            https://jira.atlassian.com/browse/JRACLOUD-85956
                => Created: 10/Sep/2021 10:25 PM
                => Affected customers: 2
                => Closed at 9.3.2022 without comments.
            https://jira.atlassian.com/browse/JRACLOUD-85963
                => Created: 3/May/2021 4:06 PM
                => Affected customers: 4
                => Closed at 9.3.2022 without comments. 
            https://jira.atlassian.com/browse/JRACLOUD-85957
                => Created: 01/Dec/2020 12:20 AM
                => Affected customers: 2
                => Closed at 19.1.20 with comment: "...that not each one will be resolved."
            https://jira.atlassian.com/browse/JRACLOUD-86661
                => Created: 16/Nov/2020 8:57 PM
                => Affected customers: 54
                => Closed at 9.3.2022 without comments.
            https://jira.atlassian.com/browse/JSWCLOUD-12898
                => Created: 02/Dec/2015 5:56 PM
                => Affected customers: 84
                => Closed at 29.8.2019 without comment. Fixed in JIRA 7.2. version. 

            Hannu Jalonen added a comment - Could you please fix this?   There are several similar reports on the subject. At least the following issues: https://jira.atlassian.com/browse/JRACLOUD-86001     => Created: 19/Jan/2023 1:15 PM     => Votes: 11     => Closed at 17.4.2024 with comment: "The behavior described appears to have been fixed at some point after this Feature request was raised:" https://jira.atlassian.com/browse/JRACLOUD-85956     => Created: 10/Sep/2021 10:25 PM     => Affected customers: 2     => Closed at 9.3.2022 without comments. https://jira.atlassian.com/browse/JRACLOUD-85963     => Created: 3/May/2021 4:06 PM     => Affected customers: 4     => Closed at 9.3.2022 without comments.  https://jira.atlassian.com/browse/JRACLOUD-85957     => Created: 01/Dec/2020 12:20 AM     => Affected customers: 2     => Closed at 19.1.20 with comment: "...that not each one will be resolved." https://jira.atlassian.com/browse/JRACLOUD-86661     => Created: 16/Nov/2020 8:57 PM     => Affected customers: 54     => Closed at 9.3.2022 without comments. https://jira.atlassian.com/browse/JSWCLOUD-12898     => Created: 02/Dec/2015 5:56 PM     => Affected customers: 84     => Closed at 29.8.2019 without comment. Fixed in JIRA 7.2. version. 

              7a341f9adb5e Ann Yan
              5c1d1b2b9112 Wil Aguirre
              Affected customers:
              8 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: