Copy Issue to Project

Release notes

Problem to solve

Currently our team's work is setup as a Group within Gitlab. We have multiple project repositories that are linked together using git submodules. We want the ability to plan our issues, tasking and backlog at the group level. Ideally we could do this by having a group issue that could affect multiple projects.

Currently we use the Issue move feature of GitLab to move issue to the appropriate project that the change needs to be made on. This works great when a change only impacts a single project. When we have a change that impact multiple projects it would be nice to have "Copy" option instead of just a "Move" option.

Intended users

User experience goal

Simplify working within a group and multiple related and interdependent projects.

Proposal

Initial implementation would be to just add a simple copy issue feature next to the move issue feature.

Further enhancements could be to allow issues to live at the Group level and link against multiple merge requests at the Project level.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

Being able to duplicate an issue onto multiple projects or associate merge requests from multiple projects with a single issue.

What is the type of buyer?

We are a Premium GitLab buyer. Technically you could psuedo accomplish this with an Epic a nested ultimate level but you would still end up having an EPIC linked to multiple issues each linked the their own request. That is a lot of duplication of tags labels, descriptions and commentary etc for something that may be a very simple task.

Is this a cross-stage feature?

Links / references