Maintain same group of Epics across two projects

[Jon A]

I have two different projects in Jira that I want to contain the same group of Epics. Is there a way to clone the list of epics in one project when I create it in the other? I don't want the issues cloned, just the list of epics. Then, when I move issues from one project to the other I'd like to see it fall under the corresponding epic.

[Mark Segall]

Hi @Jon A - Depending upon whether you've configured each project as company-managed, there is another way about this. Before I get into that, I'm curious why you need to move issues between projects.  Jira is designed for issues to be moved as an exception rather than the rule.

Anyway, if these company-managed projects, you could consider a 3rd project to act as a centralized Epic repository.  This would allow to not only maintain epics as you move issues between projects, but allow you to only have to maintain epics once.

[Jon A]

Hey @Mark Segall - I'm basically using 1 project as a repository for non-engineering / non-product folks to enter their product requests. I will then be moving requests into the Engineering backlog once everything has been cleaned up and prioritized. However, it would be great to be able to have the same list of epics across both projects so all I have to do is move the projects from one project to the next. 

These are both team-managed projects. 

[Mark Segall]

So, a couple things to consider:

1. Since these are Team-based projects, you're not going to be able to use the shared epic approach.  This is ok, because we can leverage automation
2. I would recommend cloning the original issue and closing out rather than moving issues.  Again, we can leverage automation

Your rule would look something like this:

• Trigger: Status = x
  Recommend having a status on your original issue that indicates it is ready for Engineering
• Lookup Issues action: Project = <Engineering Project> AND Epic Summary = "{{issue.parent.summary}}"
  This is a query to check and see if the Epic exists on the Engineering project)
• If Condition
  • Advanced Condition: {{lookupIssues}} = 1 
    If this passes, the epic exists on the target project
  • Clone Issue Action - Set the parent to {{lookupIssues}}
    We clone the issue and set the parent to the epic found in the lookup issues action above
• Else
  • Create Issue Action
    Create the Epic on the Engineering Project
  • Clone Issue Action - Set the parent to {{createdIssue}}
• Transition Issue Action - <Your resolved status>

[Marlene Kegel - codefortynine]

Hi @Jon A,

I am Marlene from codefortynine.

If you're want to bulk clone and move Epics, you can check out our app Deep Clone for Jira. 

If you only want to clone the Epics but not the underlying issues, I would recommend the following:

• Filter for all Epics you want to Bulk Clone in the advanced issue search
• Click on the Deep Clone button
• Define the target project and the target issue type "Epic" or "Same as original"
• Configure the rest of your clone in the Bulk Clone dialog
• Bulk Clone and Move all Epics from one project to another

[Saurabh.Sharma]

Hi Jon,

Good Day. This thread might help you https://community.atlassian.com/t5/Jira-Software-questions/Automation-Clone-Issue-into-another-Project/qaq-p/1334955

Here is the direct url of sample automation rule: https://community.atlassian.com/t5/image/serverpage/image-id/88235iADF3DED00AE13AB0/image-size/large?v=v2&px=999

Thanks,

Saurabh

[Dave Mathijs]

Hi @Jon A 

You can link a standard issue type to any Epic, also from another project. So no need copy/clone/duplicate the Epics.

If you're looking for an easy/automated way of cloning Epics from one project to another, then you'll need a third-party app as the native clone functionality always is done within the same project.

[Jon A]

Hi @Dave Mathijs - how can I do the former (re link a standard issue type to any epic, also from another project)? I'm not seeing the ability to do that in my newly created project.