Ability to track issues in multiple projects
Description
At our company we have several hundred GitLab Projects (every component, no matter how small, is its own project). We work in temporary groups with a start date and end date and a set of deliverables that need to be produced. In this description I'll call these "operations".
An Operation work on a subset of all projects using existing or new issues, but has it's own milestones. To track the progress of an Operation we usually create a new project in GitLab, create issues for each Deliverable and use links to tie issues from various projects to these Deliverables.
But there are a few problems. We can only track issues inside the Operation project in our milestones and boards. There is no way to get an overview of all issues that are interesting to the Operation. Creating duplicate issues is obviously not feasible.
We can't use groups for this and wait for group level boards (#928 (closed)) since two Operations may work on the same project. An Operation is also not interested in all issues for a project, only a few. The "group" feature of Milestones is also not working very well for us as an Operation may be interested in version 1.2 of project A and version 2.3 of project B but not version 1.2 of project C.
Proposal
- Extend the existing milestones or boards with the ability to "import" issues from other projects
- Create a new resource that work like a virtual group of projects