Create functionality for Epics (and related issues) to be cloned

Purpose

The purpose of this functionality is to make Marketing Programs processes more efficient in relation to field events. The ability to clone an epic and its related issues would significantly cut down on the administrative work required in GitLab for us to be able to organize all upcoming tasks for our long list of worldwide events. A promotion of Dog-fooding in the Marketing realm at GitLab.

If more details are required or questions arise, please comment to open discussion!

Preface

Here’s an example of an issue I would like to be able to clone: gitlab-com/marketing&212 (closed)

There is another almost exactly the same event happening a day later but I need to spend ample time creating the next epic and all related issues, due dates, DRIs, comments to MOps and FMMs.

Steps I need to complete to replicate the epic because we don’t have cloning functionality:

1. Go to Marketing epics > Create new
   • Naming convention: [Event name] - [Month] [DD], [YYYY]
   • Edit epic description with the following code

Main Issue >>

Event Details

Issue creation

• Facilitate tracking issue created - MPM
• Follow up email issue created - MPM
• List clean and upload issue created - MOps
• Landing page issue created - MPM
• Invitation and reminder issue created - MPM

1. Go to main issue and copy Event Details section from issue description

   • Example issue - this includes the YES/NO/MAYBE section filled out by FMM owner, that determines which supporting issues below I create.

2. Go back to epic and paste Event Details section from the issue into epic description

3. Create issue for facilitate tracking issue

   1. Edit issue name > Facilitate tracking - [name of event]
   2. Choose MPM-01-facilitate-tracking template
   3. Edit link to epic and insert due dates for copy deadline & send
   4. Choose DRI (MPM)
   5. Choose due date for issue as end of week WIP created

4. Create landing page issue

   1. Edit issue name > Landing page - [name of event]
   2. Choose MPM-02-landing-page template
   3. Edit link to epic and insert due dates for copy deadline & send
   4. Choose DRI (FMM owner & MPM)
   5. Choose due date for issue as copy due date

5. Create invitation and reminder emails issue

   1. Edit issue name > Invitations and reminder - [name of event]
   2. Choose MPM-03-invitations-reminder template
   3. Edit link to epic and insert due dates for send dates & copy due dates
   4. Choose DRI (FMM owner & MPM, sometimes Partner/Product Marketing)
   5. Choose due date for issue as first copy due date

6. Create follow up email issue

   1. Edit issue name > Follow up email - [name of event]
   2. Choose MPM-04-follow-up-email template
   3. Edit link to epic and insert due dates for send dates & copy due dates
   4. Choose DRI (FMM owner & MPM, sometimes Partner/Product Marketing)
   5. Choose due date for issue as first copy due date

7. Associate all issues and main FMM event issue to the epic

8. On the FMM event issue label, remove “MPM - Radar” label, and add “MPM - Supporting Issue Created” label