nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create Stories Using Automation

Katie Schneider_o2fidi

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)"

Accepted answers

Bill Sheboy

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

All comments

Bill Sheboy

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!

Kind regards,
Bill

Katie Schneider_o2fidi

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:

2021-09-27 15_49_44-Project automation - JIRA.png

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_o2fidi

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

Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud