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

Quick filter is not remembered after navigating to another board

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Problem Description

      Selecting any Quick Filter on board A, navigate to board B and go back to board A again, it used to remember the Quick Filter selection. However it is currently not working as of the latest Cloud Release.

      Steps to Replicate

      1. Create 2 test boards
      2. Navigate to board A and select Only My Issues quick filter
      3. Navigate to board B
      4. Go back again to board A

      Expected Result

      Only My Issues quick filter is remembered and selected.

      Actual Result

      Only My Issues quick filter is not selected.

      Workaround

      Manually select/click Only My Issues quick filter

            [JSWSERVER-12898] Quick filter is not remembered after navigating to another board

            it's fixed for backlog but not for "Active Sprints"

            Neal Garrett added a comment - it's fixed for backlog but not for "Active Sprints"

            We're on Jira 7.3.9 and the problem still exists in that version.  

            Celeste Plaisance added a comment - We're on Jira 7.3.9 and the problem still exists in that version.  

            Hi mrice2

            there is a workaround for 7.1.9 - https://extensi.io/agile-board-filter.

            The filter can be used instead of QFs and its state will be always saved.

             

            Cheers

            Prem

             

            Prem Chudzinski [extensi] added a comment - Hi mrice2 there is a workaround for 7.1.9 - https://extensi.io/agile-board-filter . The filter can be used instead of QFs and its state will be always saved.   Cheers Prem  

            Hi Matt,

            Seems like quick filters won't be remembered, and there are no workaround - users have to click 'My Issues'. The issue is fixed in JIRA 7.2.0 Server.

            Cheers,
            Ignat
            JIRA Bugmaster.

            Ignat (Inactive) added a comment - Hi Matt, Seems like quick filters won't be remembered, and there are no workaround - users have to click 'My Issues'. The issue is fixed in JIRA 7.2.0 Server. Cheers, Ignat JIRA Bugmaster.

            Matt Rice added a comment -

            My company just upgraded from 7.0 -> 7.1.9 Datacenter. Is there a work around or fix for this version?

            Matt Rice added a comment - My company just upgraded from 7.0 -> 7.1.9 Datacenter. Is there a work around or fix for this version?

            shayes2,

            Yes, we can confirm that the fix will be included in JIRA 7.2.

            Cheers,
            Jacek Jaroczynski
            JIRA Bugmaster
            [Atlassian]

            Jacek Jaroczynski (Inactive) added a comment - shayes2 , Yes, we can confirm that the fix will be included in JIRA 7.2. Cheers, Jacek Jaroczynski JIRA Bugmaster [Atlassian]

            Sean Hayes added a comment -

            Hi Atlassian Team, I am concerned because this has been awaiting soak since 21/Jun/2016. Over 5 weeks... Can you confirm that this is definitely included in v7.2?  Thanks!!

            Sean Hayes added a comment - Hi Atlassian Team, I am concerned because this has been awaiting soak since 21/Jun/2016. Over 5 weeks... Can you confirm that this is definitely included in v7.2?  Thanks!!

            So this is no longer assigned to an engineer. Do we have an update to when this will be resolved?

            Parker Despain added a comment - So this is no longer assigned to an engineer. Do we have an update to when this will be resolved?

            we have the problem with the selected sprint instead of the quickfilter.
            go to active sprint board, select a specific sprint. Go somewhere else and return.
            All active sprints are shown.

            Wesley Budding added a comment - we have the problem with the selected sprint instead of the quickfilter. go to active sprint board, select a specific sprint. Go somewhere else and return. All active sprints are shown.

            Hooray, a fixed version! When can we expect 7.2?

            Patrick van der Rijst added a comment - Hooray, a fixed version! When can we expect 7.2?

            Reply is much appreciated Sean

            Dani Weiden added a comment - Reply is much appreciated Sean

            Sean Hayes added a comment -

            Dani, you can select the quick filters you want, then bookmark the URL.. that's it for now. We have been dealing with this issue since the latest upgrade and it's strange that it's not a higher priority. However, I do see that work has been in progress on a fix, so that's promising!

            Sean Hayes added a comment - Dani, you can select the quick filters you want, then bookmark the URL.. that's it for now. We have been dealing with this issue since the latest upgrade and it's strange that it's not a higher priority. However, I do see that work has been in progress on a fix, so that's promising!

            This is very annoying as it's inconsistent and only happens to certain users. Upgrades to have better functionality, not worse.
            Is there an y information or setting that admins can suggest to users, or is this really a Jira bug?
            Please update this issue with some info. Tnx.

            Dani Weiden added a comment - This is very annoying as it's inconsistent and only happens to certain users. Upgrades to have better functionality, not worse. Is there an y information or setting that admins can suggest to users, or is this really a Jira bug? Please update this issue with some info. Tnx.

            When can we expect this fix for the server version?

            Korbinian Ober added a comment - When can we expect this fix for the server version?

            Reopening this issue until the fix is available for JIRA Software Server.

            Martin (Inactive) added a comment - Reopening this issue until the fix is available for JIRA Software Server.

            Verified the fix deployed on JIRA Agile v1000.0.5-D20160612T231203

            Hoang Dong (Inactive) added a comment - Verified the fix deployed on JIRA Agile v1000.0.5-D20160612T231203

            Same as above, when can we expect this to be in Server releases?

            Korbinian Ober added a comment - Same as above, when can we expect this to be in Server releases?

            Upgraded Jira server to 7.1.7 version, the same issue as well. It is reproduced in active sprint mode, in backlog quick filter is remembered (Browsers: IE11, latest chrome, FF).
            A lot of users started complaining about this inconvenience. Please solve it! Thx.

            Marian Ferendovych added a comment - Upgraded Jira server to 7.1.7 version, the same issue as well. It is reproduced in active sprint mode, in backlog quick filter is remembered (Browsers: IE11, latest chrome, FF). A lot of users started complaining about this inconvenience. Please solve it! Thx.

            Same as above, when can we expect this for server?

            Patrick van der Rijst added a comment - Same as above, when can we expect this for server?

            Sean Hayes added a comment -

            I am also deeply invested in this being fixed in the next JIRA Server release. Can you also add the FixVersion for the server release? Thanks!

            Sean Hayes added a comment - I am also deeply invested in this being fixed in the next JIRA Server release. Can you also add the FixVersion for the server release? Thanks!

            And is this also solved in server version?

            Fabian van den Barselaar added a comment - - edited And is this also solved in server version?

            Sean Hayes added a comment -

            Stanislav, Thank you for picking this up!

            Sean Hayes added a comment - Stanislav, Thank you for picking this up!

            Edo Post added a comment -

            Here we have the same issue as well, however it only occurs when changing boards from the "Active Sprints tab" when changing back and forth with the "Backlog" tab active the quick filter is remembered

            Edo Post added a comment - Here we have the same issue as well, however it only occurs when changing boards from the "Active Sprints tab" when changing back and forth with the "Backlog" tab active the quick filter is remembered

            Same behaviour for JIRA Software Server 7.1.6 using latest Chome version 50.0.2661.102 (64-bit) on OSX

            Andreas Morgner (Scandio) added a comment - Same behaviour for JIRA Software Server 7.1.6 using latest Chome version 50.0.2661.102 (64-bit) on OSX

            Sean Hayes added a comment -

            The Occurrence Factor field notes that this only affects 50% of the installations but it depends on "conditions"... can someone tell me what I need to do to be in the 50% that isn't affected? That would be a tremendous help

            Sean Hayes added a comment - The Occurrence Factor field notes that this only affects 50% of the installations but it depends on "conditions"... can someone tell me what I need to do to be in the 50% that isn't affected? That would be a tremendous help

            Sean Hayes added a comment -

            I completely disagree with the 'workaround'. This issue presents a serious usability issue for every user of our JIRA Software Instance. Especially with Kanban Boards where there are significant issue counts. Without the "remembered" quick filters, these boards become useless when navigated within the natural navigation. A bookmark with the quick filters hard coded in the URL simply does not scale. Someone (anyone?!), please escalate the priority of this issue.

            Sean Hayes added a comment - I completely disagree with the 'workaround'. This issue presents a serious usability issue for every user of our JIRA Software Instance. Especially with Kanban Boards where there are significant issue counts. Without the "remembered" quick filters, these boards become useless when navigated within the natural navigation. A bookmark with the quick filters hard coded in the URL simply does not scale. Someone (anyone?!), please escalate the priority of this issue.

            Mark Ellis added a comment -

            Found that you can use a browser bookmark as a workaround. In case you all were like me and didn't think of that previously.

            Mark Ellis added a comment - Found that you can use a browser bookmark as a workaround. In case you all were like me and didn't think of that previously.

            This is affecting us since upgrade to JIRA 7.1.4 big time please provide Workaround or fix. We will have many angry users soon

            Amir Ghaemian added a comment - This is affecting us since upgrade to JIRA 7.1.4 big time please provide Workaround or fix. We will have many angry users soon

            What is the ETA on this fix? This was a regression bug and has been impacting us for months now!

            Robert Martenfeld added a comment - What is the ETA on this fix? This was a regression bug and has been impacting us for months now!

            Our team just upgraded to JIRA 7.1.4 from JIRA 6.x and this is affecting our productivity.

            Jonathan Graf added a comment - Our team just upgraded to JIRA 7.1.4 from JIRA 6.x and this is affecting our productivity.

            Zarco added a comment -

            I agree with Korbinian Ober. It's not only an annoying bug (how came??) but it also affects productivity of my teams.

            Please get it fixed.

            Zarco added a comment - I agree with Korbinian Ober. It's not only an annoying bug (how came??) but it also affects productivity of my teams. Please get it fixed.

            We are having the same issue, 2000 users impacted - pls solve asap.

            Johan Geens added a comment - We are having the same issue, 2000 users impacted - pls solve asap.

            Kim Wall added a comment -

            We are experiencing this as well and it's a hit to users that always start from a filtered state.

            Kim Wall added a comment - We are experiencing this as well and it's a hit to users that always start from a filtered state.

            Group IT added a comment -

            We are experiencing this on Windows 7 there to 2008r2 on internet explorer and chrome and Mac OS X 10.x on safari and chrome

            My development and analytics teams are constantly complaining to me about this issues and how about it takes them longer to find there boards

            Group IT added a comment - We are experiencing this on Windows 7 there to 2008r2 on internet explorer and chrome and Mac OS X 10.x on safari and chrome My development and analytics teams are constantly complaining to me about this issues and how about it takes them longer to find there boards

            I'm experiencing it on chrome on Windows.

            Deleted Account (Inactive) added a comment - I'm experiencing it on chrome on Windows.

            I have this problem as well, but it's only when using a Mac with the Safari browser. Is everyone else who is experiencing this problem using Safari?

            Ken Strickland added a comment - I have this problem as well, but it's only when using a Mac with the Safari browser. Is everyone else who is experiencing this problem using Safari?

            Please update us on this, affecting 5000+ users here. Very poor user feedback from them due to something so minor.

            Deleted Account (Inactive) added a comment - Please update us on this, affecting 5000+ users here. Very poor user feedback from them due to something so minor.

            This is also a huge performance issue in case you have a lot of issues on the board and always have your standard filters via quick filter applied. The page load time is then about 10-15 sec. longer per board load (before update ~ 1s, after update with all issues on the board on the initial load ~10-15s, depending on the computer's javascript computation skills). I agree with the other commenters that this is much more than a minor priority. This actually affects daily work and productivity.

            Korbinian Ober added a comment - This is also a huge performance issue in case you have a lot of issues on the board and always have your standard filters via quick filter applied. The page load time is then about 10-15 sec. longer per board load (before update ~ 1s, after update with all issues on the board on the initial load ~10-15s, depending on the computer's javascript computation skills). I agree with the other commenters that this is much more than a minor priority. This actually affects daily work and productivity.

            Please fix this, this isn't minor if you get so much complaints!

            Fabian van den Barselaar added a comment - Please fix this, this isn't minor if you get so much complaints!

            James Fox added a comment -

            Complaints from my team too. A little bit of love being lost for Jira since the last upgrade on this issue. It didn't used to happen

            James Fox added a comment - Complaints from my team too. A little bit of love being lost for Jira since the last upgrade on this issue. It didn't used to happen

            AWPTV added a comment -

            Same for us. We receive lot of complaints from users in our enterprise on-premise version. Please increase the priority and get us the the same behavior as before.

            AWPTV added a comment - Same for us. We receive lot of complaints from users in our enterprise on-premise version. Please increase the priority and get us the the same behavior as before.

            This issue does not only affect the cloud version, we are also experiencing this regression in the on-premise version, currently using 7.1.0. And I agreee with the previous comments that priority 'minor' does not conform to the complaints I get from my team.

            Carlo Vollebregt added a comment - This issue does not only affect the cloud version, we are also experiencing this regression in the on-premise version, currently using 7.1.0. And I agreee with the previous comments that priority 'minor' does not conform to the complaints I get from my team.

            Agreed – this has had a big impact on my own use of Jira and I too have received a number of complaints from my team.

            Eric Seidman added a comment - Agreed – this has had a big impact on my own use of Jira and I too have received a number of complaints from my team.

            john.caron added a comment -

            While this is listed as minor, it is very annoying. I am getting loads of complaints from team members.

            john.caron added a comment - While this is listed as minor, it is very annoying. I am getting loads of complaints from team members.

              lwlodarczyk Lukasz Wlodarczyk
              rsaputra Adven
              Affected customers:
              84 This affects my team
              Watchers:
              89 Start watching this issue

                Created:
                Updated:
                Resolved: