Create Stories Using Automation

[Katie Schneider]

I need multiple stories (not subtasks) to automatically be created under an epic when it is created.

Please let me know if there are permissions I need to be aware of as when I try to create multiple stories it says "Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Parent (parent)"

[Bill Sheboy · Accepted solution]

Hi @Katie Schneider 

Would you please post an image of your rule and of the audit log showing details of the execution showing this error?  That may provide more context for the community to offer ideas.  Thanks!

Until then...some cases where that error can be shown when a field not relevant for an issue type, is not available on the edit view, and when there are timing errors getting source data (such as from the trigger issue).

Kind regards,
Bill

[Katie Schneider]

This isn't really helpful because I have changed my rule so I am not sure how I had it configured but here is the error: 

It created both my story and epic but did not link them - can someone please advise me on how the rule should look to create multiple stories (with subtasks) automatically underneath an epic when it is created?

Here is an example: 

I create epic "Kick off Call"

I want automation to create 2 stories under the epic called "Legacy Setup" and "Access"

I want automation the then create 7 different subtasks under each of the stories listed above.

Thanks in advance!

[Bill Sheboy]

Katie, I believe what is happening based on what you describe is the rule is getting confused by what "parent" is when you try to create the sub-tasks.

Focusing on just what you are trying to achieve, I have seen this solved with 1 or 2 rules.  Here is the 1-rule way.

• trigger: issue created
• condition: issue type is epic
• action: create issue, as a story, including a set of the Epic Link to the trigger issue.  Please note: Epic Link is used for a company-managed project.  If you are using a team-managed project, set the Parent instead
• action: create issue again (as you wanted 2, correct?)
• branch: on created issues (this should iterate over the stories)
  • action: create the sub-tasks

[Katie Schneider]

This solved it! I was looking for parent instead of epic link.

Thank you!

[Katie Schneider]

One last thing, how do I make it link to the trigger epic as I only see existing epics in the dropdown. Thanks!

[Katie Schneider]

I found it never mind! Thanks again!

[Lily Roy]

@Katie Schneider @Bill Sheboy 

Hi there, Could you please help me to apply the same thing :

I need multiple stories (may be place holder) automatically be created under an epic when new Epic is created.

I understand the resolution here but not sure how and where to implement it.

As I am a new user with Jira ,need your guidence.

Thanks,

[Bill Sheboy]

Hi @Lily Roy 

For a project, you may navigate to automation rules from either the lightning bolt icon on the board or from the left panel: project settings >> automation  Once there, you can create the rule to match your need.

Also, please take a look at this introductory documentation to get you started: https://www.atlassian.com/software/jira/guides/expand-jira/automation

And here is the top-level documentation for the Jira Cloud automation, with lots of great information on what is available: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

After that, you can check this library of example rules to learn some use cases and how they are implemented: https://www.atlassian.com/software/jira/automation-template-library#/

If you run into problems with your rule, please post images of your rule and the audit log, and the symptoms you are seeing.  I recommend creating a new question for that to ensure the most number of people see it.  You can then include a link to this thread so people see what you were trying to replicate.

Kind regards,
Bill