project tags should be usable in search

We have a lot of projects on our group internal gitlab server, so many that it becomes a challenge to find relevant projects.

We thought we could use the tags you can set in the project's settings in the global search for example, but this doesn't seem to work...

Would be great if those tags were part of the search, also for #2978 (moved).

Yes, useful. :)

In large organizations and governments it is extremely beneficial to tag a project with things like: owner-group-1, legacy, dotnet Project tags should be usable from the API as well, perhaps provide a way to search for projects by tag, as well as edit and apply tags by the API.

Any plans to implement this feature?

It's be useful for our company too.

Many thanks

It now requires a lot of clicks to explore the tags:

Projects -> Explore projects -> All -> Tags dropdown.

Trying this on GitLab.com also shows how limited their usability is in the current version since the list contains almost 5000 tags, and would only be useful if searchable.

In addition to making tags searchable, I would love to see tags expanded with e.g.:

• Project Settings: Same UI for adding tags as used with labels: When the user starts typing a tag, a dropdown filters through existing tags of all accessible projects, necessary to avoid lots of almost identical tags such as "gitlab ci" and "gitlab CI".
• Project view "Trending tags" or "Tag cloud".

In the meantime it seems that the project description is searchable, and adding tags there will do the job in a basic way.

Added feature proposal label

Would be very very useful. Thx

Related: Project tags do not show anywhere on the UI except in the settings

mentioned in issue #14135 (closed)

added Platform search labels

marked this issue as related to #2978 (moved)

moved to gitlab#4289

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