Jira and automation - to create epics and for each epic have Stories

[Sameeksha Santhosh Naik]

I'm new to Jira and automation and trying to create a rule. When a new Company-managed software project is created, I want to create epics and for each epic have 3 stories with a description template for all of them. Is this possible?

At this moment, I'm able to create a default epic but not stories under each epic.

[Rebekka Heilmann _viadee_ · Accepted solution]

Hi @Sameeksha Santhosh Naik 

Once you've created the Epic in the rule, you need to use a Branch "Related work items" and select "Most recently created work item".

This will make the Epic you created the "current work item" and you can create more work items with that as a parent.

[Olga Cheban _TitanApps_]

hi @Sameeksha Santhosh Naik ! 

I see you already accepted a solution that does the trick. Just in case, here's a tip: you can do this more conveniently with our app, Smart Templates for Jira.

It allows you to save any set of work items as a reusable template. Then, you can easily generate this set of tasks with a single click of a button. Also, there's a native user-friendly Scheduler, so you can generate your work items automatically and right on time.

You can easily edit your templates and share them with your team. As a bonus, they don't consume your Automation for Jira limits. 

Let me know if you have any questions!

[Lukas Nicolai_Seibert]

Hi @Sameeksha Santhosh Naik , I believe I mentioned project templates to you last time in connection with one of the use cases you raised in the community ☺️

Since you mentioned applying hierarchies like epic, story, and subtask, I also wanted to point out that we offer issue templates with Templating.app. You can apply them directly or set them up through automations.

Watch this quick guide to see how it works:

https://www.youtube.com/watch?v=xYiVFJLziNU

You can find us at the Atlassian Marketplace ➡️ https://marketplace.atlassian.com/apps/1224664 

[Clara Belin-Brosseau_Elements]

Hi @Sameeksha Santhosh Naik

Jira Automation can do a lot of things but it can also be quite limitating or hard to set up and maintain. 

As an alternative, I can suggest trying our app Elements Copy & Sync that would help you create default epics with stories when an ew project is created. 

It's really easy to set up, you can automate it with post-functions or Automation and it can clone any hierarchy of issues.

Here is a video that might reflect your specific use case: https://youtu.be/YZzq9wZ8otM?si=4WVRvnLbqAaxYFPY 

The app is for free during 30 days (and it stays free under 10 users), so don't hesitate to give it a try!

[Marlene Kegel - codefortynine]

Hello @Sameeksha Santhosh Naik,

I am Marlene, product manager for Deep Clone for Jira.

If you are open to work with a Marketplace app, you could also try out Deep Clone. With our app your use case is pretty simple to realize.

These are the steps:

• Set up a team-managed project
• Create epics and stories in this project
• Clone the team-managed project including the epics and stories (and keep their hierarchy) using the Deep Clone Project Clone

If you want to create the team-managed project manually, you could also clone and move only the work items using either the Bulk Clone or Epic/Tree Clone feature.

Feel free to reach out to us directly if you have questions about Deep Clone for Jira.

[Marc - Devoteam]

Hi @Sameeksha Santhosh Naik 

Can you show the details of your automation rule?

You could branch the rule after the creation of the Epic, based on most recently created issue.

Then create the stories and set the parent field to the Trigger Issue

Also see this KB article, automation-rule-create-an-epic-along-with-it-s-child-issues-and-link-the-created-child-issues-subsequently 

[Rebekka Heilmann _viadee_]

You could branch the rule after the creation of the Epic, based on most recently created issue.

Then create the stories and set the parent field to the Trigger Issue

Not the trigger issue (Depending on the current rule setup) but the "Current issue", which will be the Epic, as long as that's created within the same rule and scope of the branch :) 

[Yogesh Mude]

@Sameeksha Santhosh Naik  I am trying to add here is a just outline, as i have not tried this yet but i am sure that this can be done.

Assuming you have the action to create an EPIC and once the epic is created add another action called create variable and grab the recent created work item using {createIssu} or something then you can use the same variable to create a story and add Parent field with his variable.