Add 'Filter by name' to the Milestones and Labels page

Today on /dashboard/projects, you can filter your list of projects by name

We should add this same capability to filter you list to both the Milestones and the Labels page.

	Current	Proposal
Milestones
Labels		Open issue: The help text at the top of the Labels page is too long to fit the filter name input. However, I wonder if we can simplify the help text.

mentioned in issue #21747 (closed)

I feel like I've seen the suggestion to add 'filter' to the Labels page before, but couldn't find it. Not sure about the milestones page. I created this issue in response to the comment here: https://gitlab.com/gitlab-org/gitlab-ce/issues/21747#note_21488276. Let me know if it is a duplicate. Thanks!

mentioned in issue #23164 (moved)

mentioned in issue #14520 (closed)

added frontend ~974571 feature proposal ~423634 ~163085 and removed ~19492 labels

@victorwu - This is a frequently requested feature and something we need to add.

@awhildy : For labels, let's improve the page after the performance fixes are in.

For milestones, do you know how that milestones page is used primarily? If we want a list of issues in a milestone, we use the list view primarily?

mentioned in issue #29343 (moved)

@victorwu This came up again. https://gitlab.com/gitlab-org/gitlab-ce/issues/28836#note_25143795

I created a separate issue to be able to filter by subscribed labels https://gitlab.com/gitlab-org/gitlab-ce/issues/29343

For milestones, do you know how that milestones page is used primarily? If we want a list of issues in a milestone, we use the list view primarily?

The milestone page is used to view the progress of the milestone in it's entirety. Being able to search for a specific milestone would help because then you can more easily find a milestone that you want to drill down into to see the breakdown of not only issues but also merge requests. You can also view participants and labels used.

Thanks @tauriedavis . Let's get back to milestones when have more feedback (unless you already see a lot, I'm not seeing much.)

We do have issue boards per milestone in 9.0, and burn down charts in milestones for 9.1. So I do anticipate milestones will pick up usage soon and this is definitely something we should consider in a few releases out.

Sounds good - thanks @victorwu!

mentioned in issue #31543 (closed)

mentioned in issue #32676 (closed)

mentioned in issue #33993 (closed)

Are there any updated plans to fix this? Any ETA? I'm coordinating a possible migration to GitLab by the GNOME project and label scalability/manageability has been raised as a concern.

@victorwu I think this feature proposal could be opened for a Community Contribution with Accepting Merge Requests. The UX is ready to go and it seems that we're all in favour of the new functionality.

@smcgivern : Are there any performance considerations here?

@victorwu I think it should be good.

I've added the label and a weight.

added Accepting Merge Requests label

Hello I'm new to contributing here on gitlab and wanted to help out, just confirming, this is still available to work on right?

@jcgalbano yes, this new feature is wanted and will be accepted once it's ready.
Please create a new merge request and do your work there.

Okay thanks!

I've managed to make the "Filter by Name..." in both the labels and milestones pages but was not able to do it in ajax, can't seem to wrap my head around gitlab's codebase just yet. Can we divide the merge requests into, 1. Basic functional search (needs to reload to actually search) to make it readily available + 2. Ajax implementation (just like in the projects page).

Sorry took me a while, the gdk both amazed and challenged me at the same time lol

@ClemMakesApps Can you take a look at @jcgalbano's comment above?

@jcgalbano Do you have a link to the MR?

@jcgalbano if you can create a MR to this repository, we can try to help you out. Depending on complexity, breaking it out into two parts could make sense but until we take a look at the code, it's still hard to make a decision on it

mentioned in issue #35287 (moved)

cc @victorwu

changed milestone to %Next 2-3 months

marked this issue as related to #35287 (moved)

mentioned in issue #38321

moved to gitlab#7901

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