Can I create a templated group of Story's in Jira that can be cloned and added to existing EPICS?

[Mathew Martin]

Hi,

I currently have a Jira board where jobs flow in from a form as EPIC cards.

As part of these EPICS we have defined a group of STORYs that need to be completed in order to complete one type of EPIC. In-fact, there's 23 STORYS however not all the EPICS will require all the 23 Story's I've grouped. 

I'd like to to understand how I can have that templated group of Story's that can be copied and linked up to a new EPIC.

Specifically the STORYs on my board I want to group as a template are GRC-108 to  GRC-131. That grouped template of story's I want to be able to clone and link the clone to existing EPICS. Once those story's are linked to the EPIC I'd like the ability to either update or remove any of those 23 Story's within that EPIC. 

Is anyone able to help me do that? 

Kind regards,

mat

[Yuliia Tkachenko _Railsware_]

Hi @Mathew Martinwelcome to the community! 

Smart Templates for Jira can help you with that! This app lets you to create and manage templates for any issue type, including Epics and Stories. You can customize templates with pre-filled fields, dynamic values, and automate issue creation with a scheduler or using Automation for Jira. Also, History tab will provide you links and info on all the created issues from a template in one place. Smart Templates can significantly reduce the time spent on repetitive tasks and ensure consistency across your projects. 

Alternatively, you can try managing this process using Jira issue cloning functionality. Please note that in this case it won't be saved as a template. 

Hope it helps!

[Trudy Claspill]

Hello @Mathew Martin 

Welcome to the Atlassian community.

If you don't want to use a third party app, you could do something like that with Automation Rules. Are you familiar with that feature?

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

The rule trigger would be Issue Created.

You would add a condition to confirm the issue type of the created issue is Epic.

You could use a Lookup Issues action to retrieve (via JQL) the issues you want to clone.

You could use a Smart Value branch to iterate through the list of found issues and clone each one, and change its parent to the trigger issue.

Are the new Epics also in the GRC project? And would the issue created by cloning also be in the GRC project?