Can I setup a rule that on project creation an epic, stories, and subtasks are created?
Asked by Carson Mishoe:

I am trying to create a rule in Jira automation that allows me to make an epic and corresponding stories and subtasks.

For example:

On project creation:

Create Epic

Create Story under that epic

Create Subtask under that story

Would like help thank you


Answers:
author: Carson Mishoe
body: ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/334472i7941C9D4EDDE4354/image-dimensions/293x667?v=v2 "image.png")

For Creating stories \^

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/334472i7941C9D4EDDE4354/image-dimensions/293x667?v=v2 "image.png")

For creating subtasks under those stories \^  

Our team decided we would not do project creation but instead epic creation.

We basically checked if the Epic has the summary we would always use, then would create stories under that epic.

After we created another rule that checks the Story names. We would always use the same names so it would be fine. We weren't able to figure out the project creation stuff but its not longer needed. Thank you for the help :)


author: W_Diehl _Litew8 GmbH_
body: Hello [@Carson Mishoe](/t5/user/viewprofilepage/user-id/5540062)

as others have pointed out, Jira's native automation rules would be the go to option for custom issue creation. But sadly when it comes to automatically creating issues after project creation there is only a 'Project created' trigger but you can't specify a project category, so the issues would be created in every new project. If that's what you want, go for it.

Otherwise, since you are on a free Atlassian license, I would recommend you looking into extensions on the marketplace. For example is our app built for your use case and free for instances under 10 users.

[**Project Templates for Jira**](https://marketplace.atlassian.com/apps/1230303/project-templates-for-jira?hosting=cloud&tab=overview) allows to easily create a custom project template, add the project configuration and predefined epics, stories and sub-tasks all linked together and everything else you want to it. From then on, every time you need another project with said configuration and issues, you can just use the custom project template to create it.

Give it a try and let us know if you have any questions.


author: Trudy Claspill
body: Hello [@Carson Mishoe](/t5/user/viewprofilepage/user-id/5540062)

Welcome to the Atlassian community.

You could do this in a manner that works for Company Managed projects, but not for Team Managed projects.

There is a [Project Created trigger](https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Project-created) that you can use to detect that a project has been created. Because the rule can not have a predefined Project Scope you would have to create that through the Global Automations page available from the System administration area.

You can then add tasks to create an Epic, child story, and child subtasks.

<https://support.atlassian.com/jira-service-management-cloud/docs/edit-your-service-project-details/>

There are some finer details, such as how to make the newly created story a child of the Epic you just created, and how to create Subtasks under the newly created story.

Would you be creating the same subtasks under each story?

It might be easier to do this through multiple rules. Perhaps one to create the Epic, which will trigger another that will create the child issues, and then a third that will create the subtasks.

Have you given it a try? What have you constructed so far? What steps are stumping you?


Tags: cloud

jira-cloud