You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I click Quick Filter, named "Recently Updated" and leave the page on Jira Software Cloud version. Then, the quick filter does not remain when I visit the same page again although "Recently Updated" looks still pushed. Do I need some settings to keep quick filter applied?
Jira Server keeps quick filter when revisiting pages.
I know similar issue is reported in the question "Remember quick filter and issue filters when leaving page" and it has been fixed, however I have the problem.
[When clicked]
[After revisit]
@Masayoshi Tsuchinaga , welcome to the Community. I haven't really every paid much attention to this TBH. I don't use quick filters all that frequently. However, I just went out an did a quick test and what I experienced seems like a bug.
Here is what I did.
Test 1:
Test 1 observations:
The filter was still highlighted as selected however the resulting issues were clearly showing that no QF was selected.
Test 2:
Test 2 observations:
This time the QF seems to still be in effect.
So IMO there appears to be a bug here and will report this to Atlassian Support to see what they have to say. IMO, I would prefer that QFs not remain sticky. If they do then it needs to be a per-user situation for sure. Regardless of "to sticky or not to sticky" it needs to be consistent.
FWIW, I found a similar suggestion in JAC (JSWCLOUD-10258 ) but it is a bit different and my real concern here is that the behavior is inconsistent when navigating away and back to a board.
Sorry for my late reply and I appreciate you have answered quickly.
I did as the following and the result is the same as your Test 1.
I agree inconsistent behavior should be resolved and I guess users of Jira Server version who plan migrating to Cloud version want a behavior as Server version (namely your Test 2 case) as we.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Coincidently, I had a screenshare session w/ Atlassian support yesterday. He agreed that the behavior was inconsistent and was going to raise it to development to see if they agree and if so raise a bug. If I hear back w/ a ticket number I will add it here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Masayoshi Tsuchinaga , I just heard back from Support and they have opened a bug for this that you can watch if you wish - https://jira.atlassian.com/browse/JRACLOUD-75575
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the information. I will watch the bug ticket you mentioned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.