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; } } }

Issue with Sub-tasks automation need parent ID error

Alicia Simon

I am trying to create an automation that creates a new issue within a project and within that new issue create two sub-tasks. The issue is created successfully, but I receive errors regarding the sub-task creations: Issue type is a sub-task but parent issue key or id not specified. (issuetype).

JIRA-Ranches MonthlyFinancialsError.png

Yet in the automation rule I have the parent issue set as "Current Issue". How do I get the automation to create the sub-tasks within the issue that is created?

Thank you,

Accepted answers

All comments

Trudy P Claspill

Hello @Alicia Simon

You can use a smart value to set the Parent of the subtasks. Example:

Screen Shot 2023-05-10 at 2.40.39 PM.png

Because you are created multiple subtasks I would recommend you do this:

After the creation of the parent issue and before creating the first subtask:

1. Add a Re-Fetch Issue action to ensure the parent issue creation has completed.

2. Add a Create Variable action to store the key of the created parent. The value you want to store is {{createdIssue.key}}

Then, in the Create Issue actions where you are creating Subtasks, set the Parent Issue field to the smart value for the Variable you created.

Alicia Simon

Hi @Trudy P Claspill ,

I tried your suggestion and while it made sense, the result I got is confusing.

Instead of creating one issue with two sub-tasks, the rule created two new issues, each with the first sub-task and also two new sub-tasks under unrelated existing issues (68 & 41).

I also receive an error regarding creating the second sub-task of the rule.

Results:

Here is what I have in the rule (if there's a better way to show, let me know).

I'm beginning to think I just need to create individual issues and not worry about sub-tasks, but I was hoping to keep the board cleaner this way.

I appreciate your help.

Trudy P Claspill

Hello @Alicia Simon

The unexpected results have to do with your trigger.

In your Scheduled trigger you have included a JQL. When you include a JQL in your Scheduled trigger you are telling the Automation that those are the issues you want to operate against. The steps in the automation will be executed for each issue returned by that JQL.

Since your JQL found two matching issues, it will loop through all the actions in the rule twice; once for each issue found.

I don't think you want that. If you think you do then I have missed something in you explanation, and can you please explain how creating a new issue and subtasks relates to the issues you are selecting with JQL?

If indeed you don't want that, then remove the JQL from the trigger and try running the rule again.

Alicia Simon

I have tried to create it without the run a JQL box checked but I always get an error. In this case here is the error I get.

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

atl-gruland

automation