Issues list search and filters bar

added search label

@victorwu: Here is the list of next steps for us to prioritize with the search bar work. While some of the high priority items may seem small, this is a feature where the micro-interaction details are key for it to really shine and feel great. Thanks!

added ~874211 ~14281 ~13921 labels

Thanks @awhildy

Let's revisit this and scope out the next iteration once 8.15 is officially released and see what is clearly working on GitLab.com.

mentioned in issue #26098 (closed)

changed title from New search/filters bar - Second iteration to Issues search/filters bar

mentioned in issue #26652 (closed)

mentioned in merge request !7345 (merged)

mentioned in issue #26670 (closed)

@victorwu: This issue came up in a conversation with the UXers at the summit (@cperessini @dzaporozhets @dimitrieh @tauriedavis @pedroms @sarahod). The concern came up about not implementing the same design on the Merge Requests list (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests) that we have on the Issues list. There is a feeling that these two list pages should be kept in sync. @dzaporozhets mentioned that it should be pretty easy from a technical perspective to translate the current design to the Merge Request list. Do you have an idea of how much work that is, thoughts on that priority, and if we can get that done sooner rather than later? Thanks!

@awhildy : Yep, this makes sense. Basically should we go deep first or wide first?

My initial thoughts are that we should do a few more iterations on the issues side first before porting the design over to merge requests (that's the existing order in the issue description above). That way we can compare the two designs in production. And if we have to tweak the design based on feedback, we can do it in one area, get it to a steady state, and then port it.

The alternative is to go wide first, and port to merge requests with whatever we have. This is driven more by consistency as soon as possible, I guess?

I don't have strong opinion either way. Either way, we'll prioritize something (see https://gitlab.com/gitlab-org/gitlab-ce/issues/26259). I'm pushing for next iterations on 8.17.

Engineers can comment on effort required.

I think it makes sense to bring it over to MRs after the first iteration from a usability standpoint, we would just want to have better test coverage to make sure nothing gets missed. It's not trivial but its not extremely difficult to do.

We have a few ideas for next steps to improve usability at the top in the description. Let's aim for this in 8.17 and anything else that we can determine are major usability pain points. And then let's port to merge requests as a stretch goal. But for 8.17 I'd say let's get it to stable place where everyone is comfortable with the basic usability: https://gitlab.com/gitlab-org/gitlab-ce/issues/26749.

Adding arrow keys would be really helpful!

mentioned in issue #26785 (closed)

I would say it should be brought to MRs as soon as possible after issues. Having different UX on basically same pages is annoying to me.

Nice! A filter for participants of an issue would be also very helpful for us

I've created both #26840 (closed) and #26841 (closed)

I've also created https://gitlab.com/gitlab-org/gitlab-ce/issues/26844 (New search bar performs a new request for each 'tag'), if someone could add mine and ZJ's issues to the list above, that would be great!

Thanks @zj + @smcgivern. They are in the list. I'll update the priorities a bit once we get some more discussion / feedback from UX.

If we move the search bar to the MR tab, is that the only work we can plan for in 8.17? Trying to balance largest usability concerns with easiest to quickly address. Thanks!

mentioned in issue #26749 (closed)

added meta label

marked the task #26882 (closed) Hard to filter by "Me" with current filter dropdown as completed

marked the task #26884 (closed) Issues: broken issue search / filtering + new issue search totally sucks as completed

marked the task #26841 (closed) No tabcomplete on search suggestions as completed

marked the task #26959 (closed) Added current user filter to assignee dropdown as completed

marked the task #26955 (closed) Filter issues input does not show assignee name when there is an assignee ID in the URL as completed

marked the task #26617 (closed) Search bar filter dropdown does not dismiss when sort dropdown is selected as completed

marked the task #26623 (closed) Search bar dropdown doesn't load when you go back in browser history as completed

marked the task #26785 (closed) Search bar not working on IE as completed

marked the task #26623 (closed) Search bar dropdown doesn't load when you go back in browser history as incomplete

marked the task #26623 (closed) Search bar dropdown doesn't load when you go back in browser history as completed

mentioned in issue #26945 (closed)

mentioned in merge request !8681 (merged)

mentioned in issue #27057 (closed)

@victorwu Just to give you a heads up, we now have some videos of users interacting with the issue filter. I have 2 videos so far, which I've analysed and I hope to have the final 3 videos by the end of tomorrow. You can find my analysis within my [research plan] (#26945 (closed) ).

You will also find in the plan, direct links to the videos on YouTube. I've timestamped them so you can skip to the most relevant bits imo.

If you want to discuss any of the research (e.g. why tasks are worded in a particular way) then do feel free to schedule a call with me.

Thanks @sarahod . I'll review this soon hopefully today or tomorrow, and based on that, clean up some issues here and you can help with some of the priority of major pain points. Thanks!

@victorwu see also #27057 (closed) and #26835 (closed) which aren't covered in this issue.

marked the task #26670 (closed) Auto space and dropdown in issues search bar as completed

marked the task Can’t multi-select labels with mouse, can only do it by typing - attempting to do it via mouse unexpectedly clears currently selected label filter as completed

marked the task Once label is typed in search field, clicking back in search field doesn’t display all top-level filter options, only labels - have to press space to get all other options as completed

marked the task Clicking on "Keep typing and press Enter" should perform the search as completed

@victorwu looks like @iamphill already got filter dropdowns to open based on where the cursor selection is. Do we want the big goal for %8.17 to be to move the filtered search to the merge requests page?

marked the task #26652 (closed) View and edit tokens in issues search bar as completed

@ClemMakesApps : I think https://gitlab.com/gitlab-org/gitlab-ce/issues/26652 hasn't been solved yet? I added a comment there. After that, I agree it's stable enough to move to merge requests page. I'll add an issue and put it in the description.

mentioned in issue #27131 (closed)

changed title from Issues search/filters bar to Issues list search and filters bar

mentioned in issue #24688 (closed)

mentioned in issue #21747 (closed)

marked the task #26652 (closed) View and edit tokens in issues search bar as incomplete

@ClemMakesApps we also need to address the issue that @smcgivern brought up. Very important. Can we take a look at that regression first?

yes @jschatz1, that MR is already in review

mentioned in issue #27235 (moved)

mentioned in issue #27238 (moved)

mentioned in issue #27239 (moved)

mentioned in issue #27286 (moved)

mentioned in issue #27293 (closed)

marked the task #26840 (closed) Searching issue filters should be keyboard selectable as completed

marked the task #26844 (closed) New search bar performs a new request for each 'tag' as completed

marked the task #27176 (closed) Filtered search bar assigned to me option as completed

marked the task #26670 (closed) Can't multi-select labels with mouse, can only do it by typing - attempting to do it via mouse unexpectedly clears currently selected label filter as completed

mentioned in issue #27262 (closed)

mentioned in issue #27747 (moved)

mentioned in issue #27414 (moved)

mentioned in issue #27261 (closed)

mentioned in issue #22921 (closed)

marked the task 9.0 #27131 (closed) New interface for merge requests list search and filter as completed

mentioned in issue #29362 (closed)

mentioned in issue ux-research#1 (closed)

Do we have an issue for rolling this out to Groups and Dashboard?

Maybe we should reference this issue:

https://gitlab.com/gitlab-org/gitlab-ce/issues/29532

marked the task 9.0 #26652 (closed) Add token UI for filtered search bar as completed

marked the task #22921 (closed) Show current user immediately in filters as completed

marked the task #28312 (closed) New interface for boards search and filter as completed

marked the task #27174 (closed) Frontend allows to filter issues by 2 milestones although it is not possible as completed

marked the task #27293 (closed) Applying the same filter twice in the issue filter as completed

This is a lot of stuff. @victorwu should we prioritize fixing this for %9.2

marked the checklist item #27262 (closed) Add option to store recent history of the filtered search as completed

@jschatz1 : What do you mean? We have a few issues I think for improving the search bar. Like the label colors and introducing the xs. Nothing urgent here I think?

mentioned in issue #30891 (closed)

@victorwu then should it be closed?

@jschatz1 : Why close? No more meta issues you mean?

mentioned in issue #31370 (closed)

@victorwu well I guess we should figure out if it should go in the backlog then? If nothing is urgent?

If nothing is urgent?

I'd love to have #27747 (moved)

@victorwu please consider including https://gitlab.com/gitlab-org/gitlab-ce/issues/31949

mentioned in issue #19808 (closed)

mentioned in issue #34884 (closed)

moved to gitlab#7524

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in issue gitlab#7974

mentioned in issue gitlab#7976

mentioned in issue gitlab#7977

mentioned in issue gitlab#7991

Issues list search and filters bar

Resources

Issues

Designs

Child items ...

Activity

Frequently Asked Questions

Admin message

Admin message

Issues list search and filters bar

Resources

Issues

Activity

Frequently Asked Questions