Skip to Main Content
Status Future consideration
Categories Epic
Created by doug evans
Created on Mar 19, 2019

Copying an epic should also copy the associated Features.

Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense. 

  • Attach files
  • Kristina Ursin
    Reply
    |
    Mar 1, 2023

    I'd envision this to be similar to when you duplicate a Feature or a Release where it duplicates all the Requirements or Epics/Features respectively, except that for the Epic it would have a pop-up with a check box for each related Feature that could be unchecked if that particular Feature should not be duplicated. This would be a huge time saver, as the current workaround of duplicating a Release duplicates EVERYTHING in the Release AND creates an addition un-wanted Release.

  • Guest
    Reply
    |
    Jul 20, 2022

    We noticed this has been pending since 2019, would be a huge win for everyone using this tool to plan and manage their work. Would enable leveraging previous work / reduce duplicative entry if this functionality is added (Copy Projects includes all related deliverables option).

  • claire Kennedy
    Reply
    |
    Mar 18, 2022

    When managing a partners building to our API, we often recommend they build the same set of features, and we support them through the various stages of build, testing & release of each. Currenlty we have an Epic per partner and then list each feature in the epic. We then add the epic to the release. It would be great to be able to clone an epic AND its features, to save time in this process. Another potential solution could be to allow release templates to also create Epic and features

  • Erica Witte
    Reply
    |
    Nov 3, 2021

    Copying all elements, especially Stories, under an Epic is an expected functionality when copying Epics; otherwise, users would just copy lower-level elements.

  • Abby Smith
    Reply
    |
    May 4, 2021

    This would be a great option for our workspaces since we have templates that we use when creating new records and it would be really convenient to copy all of features/activities under each epic instead of having to do it individually.

  • Guest
    Reply
    |
    Mar 8, 2021

    This would be major time saver, I have a epic in mind called product launch = that epic has always the same features/activities for delivering product launch

  • Dave Tucker
    Reply
    |
    Oct 5, 2020

    This would be a great time saver and also provide greater consistency to team members responsible for executing projects in the same way.

  • Pam Matula
    Reply
    |
    Aug 7, 2020

    I'd also like to see this functionality as an option. In our Marketing workspace, we have 'templates' for release activities that are repeated with each project. It would be great to be able to build and copy these to save time.

4 MERGED

The ability to copy an epic and the features are copied with it.

Merged
Having the ability to copy a master feature and the features attached to it copy with it. This will be useful for template items for efficiency of time. Similar to how a release can be copied but maybe a notification option pops up when you click ...
Guest almost 5 years ago in Ideas 0 Future consideration
2 MERGED

Allow 'deep cloning' of epics

Merged
Cloning an epic doesn't copy any of the stories that are part of it. Right now we use a 'template' story, that we just clone. I'd like to be able to make a template for epics that have pre-defined stories.
Guest over 3 years ago in  2 Future consideration