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

Error running basic automation on next-gen project

Adam Foot

The goal is to create an automation that when run creates a Task with Subtasks.

To try & achieve this, I've created a very simple automation task configured as follows:

Create a new issue in:

Project: Test

Issue type: Task

Summary: task test

Create a new issue in:

Project: Test

Issue type: Subtask

Parent Issue: Current issue

Summary: subtask test

However when run, it shows the below output including an error at the subtask step:

Action details:
Create issue
Issues created successfully
TEST-32
Create issue
Error creating issue
Issue type is a sub-task but parent issue key or id not specified. (issuetype)

Please advise what the problem is here?

Thanks

Accepted answers

Ash Pitt

Hey @Adam Foot

I believe you would want to select the "Create sub tasks" action.

Basically

When: Issue created
Condition: Issue type equals task
Action: Then create x sub tasks

That should do it

All comments

Ash Pitt

Hey @Adam Foot

I believe you would want to select the "Create sub tasks" action.

Basically

When: Issue created
Condition: Issue type equals task
Action: Then create x sub tasks

That should do it

Adam Foot

Thanks @Ash Pitt for the prompt reply.

I did see that option, but the problem I encountered is that it doesn't let you set additional properties on the create sub-tasks action page e.g. assignee.

When I click on add fields it takes me back to the standard create issue page where I had originally configured the subtasks & therefore have the errors.

Here is a snip of what I'm trying to achieve - it begins off a scheduled time trigger:

Based on the above, would there still need to be conditions added?

Thanks

Ash Pitt

Hello again @Adam Foot

I only added in the condition to specific adding the task type only, so it's not required really, that's just how I'd filter it down to "task only".

To assign a user I just used the "add fields" part of the sub-task automation and was able to automate the assignee to the reporter. There are plenty of other options though!

So it looks like you're on the right path, just play around with the "Add fields" options.

IMO to test the function out first (if you haven't already) do the automation triggers based on when the issue is created, then when happy, flick to scheduling.

Cheers

Ash

Adam Foot

Hi @Ash Pitt I'm unfortunately still getting the error when running the very basic automation shown in my previous post. The error details are below:

Any ideas?

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

automation

schedule