Make it possible to copy issue search filters

Description

Currently it is possible to paste into the issue search field but not to copy from it.

Proposal

Add a Copy to clipboard button to the search field:

/cc @victorwu

It would also be nice if you could select them via keyboard and mouse. So you could delete or copy only a part of them.

@maxraab Yes, I agree. You can already click an delete them individually but not cut or copy.

delete-search-token

@winh Thank you! Another pretty hidden feature of GitLab ;-)

The default behavior of all other text boxes would be cool. Selecting via mouse click-and-hold-move and navigation via keyboard with ctrl + arrow keys and selecting via ctrl + shift + arrow keys.

We already have recent searches. Something like this makes the searches a bit more "exportable", which is great.

But the natural use case that I see is simply copying and pasting the entire URL. Doesn't make sense to load the issues page and then pasting the filters as text into the search bar.

So from that sense I don't see a whole lot of value in this feature. The main benefit is that instead of copying your own current browser bar URL, you can copy it to your clipboard with one click.

@victorwu In my opinion, a major use case for this is to use same filter criteria across projects (for example CE and EE in our case).

mentioned in issue #30468 (closed)

@winh : It's not guaranteed that projects share filters (i.e. different labels and milestones, etc.) But the more root problem is we should be using group lists and group features in general. Those still need a lot more work. So I'd rather we iterate on group features instead of creating point solutions that doesn't address the root problem.

mentioned in issue #31859 (moved)

moved to gitlab#9663

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