Move an epic to a different group

Problem to solve

Sometimes the scope of an epic changes to affect sibling groups / the parent group). The current workflow for those cases is to create a new epic and copy all issues individually, which leads to a poor user experience.

Intended users

Everybody who works with epics—so mostly managers but also developers.

Proposal

Create a /promote quick action that copies the epic (along with all comments, labels, issues, and child epics).

After the action, issues will only be linked to the new epic and no longer to the old one (because each issue can only belong to one epic). See also https://gitlab.com/gitlab-org/gitlab-ee/issues/4001.

Permissions and Security

This action may expose confidential information if the child group is private but the parent group is public. We need to at least have a note (similar to moving issues).

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

It's possible to move / duplicate epics to parent groups.

What is the type of buyer?

Manager / Director