Add "Project" filter to global views
Global views show Activity, Issues etc for all projects, but there is no "Project" filter.
In "global issue" view, there is "author", "assignee", "milestones" and " label" filters : there should also be a "Project" filter.
In "Activity" view, there should also be a "Project" filter
And in all global views where it's meaningfull.
And when the filter selects a project, there should be an easy way to change the global scope to that specific project scope.
Activity
Hi @JLuc,
First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria:
- No activity in the past 4 months
- Unlabelled
- Unassigned
- It's not associated with a particular milestone
We'd like to ask you to help us out and determine whether this issue should be reopened.
If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.
If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.
Thanks for your help
With detailed urls :
- there IS a "project" selector in global "todos" : see https://gitlab.com/dashboard/todos : that's great !
- in global "Issues" pane https://gitlab.com/dashboard/issues, there are a few usefull selectors but NOT the "Project" selector : there should also be a "Project" selector
- same with "Merge requests" https://gitlab.com/dashboard/merge_requests
- in global "Milestones" : see https://gitlab.com/dashboard/milestones there is no selector at all : that pane could be enriched with selectors
Edited by jluc
Thanks @JLuc and @winniehell! I definitely agree that we should be consistent here, and I think we should allow filtering by project on all of these pages.
We currently are working on overhauling the filtering UX (#21747 (closed)), and that should help in situations like this. We are starting with the Issues page, but the plan is to update the filters UX across GitLab, including the pages you mentioned above. When that happens, we should add the ability to filter by project. @cperessini: Let me know if you see any concerns with that. Thanks!
cc @victorwu I'm not sure this is actually ~"coming soon" soon. Will we be adding the new search to the global views soon? Does it make sense to add a Project filter in the mean time? Let me know how this fits in from a product perspective.
@tauriedavis : I removed the label.
added ~2975006 and removed typebug labels
mentioned in issue #40155 (closed)
marked #40155 (closed) as a duplicate of this issue
From #40155 (closed): It would be nice to not only have „project“ but also „groups“ (there already is this for a single group). A preset for „all projects I am part of somehow“ would also be nice (my use case).
added [deprecated] Accepting merge requests label
added devopsplan label
Hey!
GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current
gitlab-cerepository will become a read-only mirror, without any proprietary code. All development is moved to the currentgitlab-eerepository, which we will rename to justgitlabin the coming weeks. As part of this migration, issues will be moved to the currentgitlab-eeproject.If you have any questions about all of this, please ask them in our dedicated FAQ issue. 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 theee/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.
