Hard to use issues filters, loose config between pages
Hi
Recent user, so maybe I'm missing something, but I find current Gitlab (CE - 8.6.1) behavior very uncomfortable to use, in that the filters on the issue page (which I use most), do not retain their state between page loads. Assume the following scenario:
- display issues for project A
- filter by a given Milestone (Version 1.1) and label (Bug)
- click through one of the issue (, move it to another milestone or close it
Now, unless I'm mistaken, to go back to the list and process the next issue, you can only:
- hit the browser back button -> filters still have their state (Version 1.1 and Bug), but the closed or moved to another milestone issue is still there, because we are just seeing a cached version and the page has not been reloaded
- click on the "Issues" link at the top of the page, or in the left menu bar: in both case, the close or move issue has now been updated, but the filters have lost state, and we have to reselect Milestone and Label to get back to live list.
Could the filters state be preserved in the session, as is usual with CMSes? Going back to the Issues page of a project from another page should retain the filters that were last selected.
Same could apply to:
- Files: store the current folder in session, so as not to have to navigate back to a possibly many clicks away folder
- Commits: retain the selected branch
- Merge requests: retain filters
And of course, the stored state has to be per project.
Thanks for your consideration.
Rgds
Activity
/cc: @jschatz1
I think this hits the nail on the head. @iamphill Let's talk about how to implement properly.
-
@weeblr Right now:
do not retain their state between page loads
They do now.
Other issues here still need to be addressed.
Edited by Jacob Schatz 
Hi
Thanks for your reply. I can see the filters retain their state when hit the reload button. I didn't notice actually, as this is not really where I needed improvements. Just to be on the same wavelength:
- I use latest 8.6.6 of CE
- Filtering on a milestone
- I click through to an issue
- go back to issues list with either
- back button
- clicking on the Issues link in sidebar or top link
That still left me with filters all reset. That's still the expected behavior?
Rgds
Reassigned to @iamphill
@iamphill I thought I saw another issue that worked on the same problem not?
-
@weeblr we will be rethinking filters and search in the following meta-issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/21747
-
@dimitrieh Thanks for pointing that out. Let's cross fingers, triaging issues with the current filters not saving their state across page loads extremely frustrating to say the least. Especially considering saving their state in the session is pretty trivial.
Likewise, are you aware of any discussion on the menu system? where you need to load an intermediary page ("Issues") if you are, say, looking at a file content and want to navigate to the builds page or anything on the menu secondary-level. That should be a javacsript/CSS simple sub-menu instead, to avoid loading full page just to be able to view the "Builds" menu link and click on it!
Rgds
mentioned in issue #22069 (closed)
-
Mentioned in issue #22069 (closed)
-
@weeblr could you close this issue? as there are already some of these issues handled in separate issues :) If you have additional things you would love to see handled, please make individual actionable issues for those, so we can discuss more focussed
-
Hi
@dimitrieh I wouldn't mind closing this issue if anything related to it was happening, or event just started to be discussed. But in seven months, nothing has changed, what I experience daily as a real pain, frustating, time-wasting experience has not been adressed at all.
I'm not closely following other issues I am not involved in, so if any progress is being made in other issues on the matter described here, please be kind to link to them.
Rgds
-
@weeblr I totally get what you say :) However this issue is not quite actionable as it lists several problems at once in different areas. The solution to a problem is to focus your problems 1 at a time, create a separate issue for each problem on its own which can then be tackled. You are in luck as quite a few of your points already have issues for them. I can only encourage discussing or committing code to those.
https://gitlab.com/gitlab-org/gitlab-ce/issues/21747 handles quite a lot of the search/filtering pains that currently exist (incoming next release most probably!)
Issues that are related to having persistent filtering across pageloads are also mentioned there, example is https://gitlab.com/gitlab-org/gitlab-ce/issues/21429
The Navigation problem is tackled here: https://gitlab.com/gitlab-org/gitlab-ce/issues/22069 (being actively discussed by the UX team)
You could create an issue for:
hit the browser back button -> filters still have their state (Version 1.1 and Bug), but the closed or moved to another milestone issue is still there, because we are just seeing a cached version and the page has not been reloaded
and mention it in #21747 (closed)
I will be closing this issue to move discussion towards places where it matters the most :)
Please tell me if I missed any :) and if so make a bullet point list with each problem listed separately.. we can find or create issues accordingly.
-
Hi @dimitrieh
Sorry, you lost me here. This issue was strictly about one item:
in that the filters on the issue page (which I use most), do not retain their state between page loads.
In other words, exactly what you just agreed has been totally left out:
hit the browser back button -> filters still have their state (Version 1.1 and Bug), but the closed or moved to another milestone issue is still there, because we are just seeing a cached version and the page has not been reloaded
In case you didn't notice, hitting the back button is a page load.
#22069 (closed) is unrelated (I am also part of this discussion. Well, I was) #21429 (moved) is a duplicate of the current issue (except it's only 2 months old, instead of my 7 months old one, and it adds Boards to the mix, which didn't exist when I started).
I hope #21747 (closed) will bring in good things, but I'm sorry, I'll stop wasting time here.
Rgds
