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 an automation rule to create multiple tasks based on description

Sujatha Venigalla

Using Automation, how to create multiple tasks under a parent task dynamically based on the description of the parent task

Eg.

Description Contains

Create 3 tasks for below and assign accordingly. These assignees might not be100% match with Jira Assignee as I might not write down complete full name

Gather Requirements - Assignee1

Develop Code - Assignee2

Test - Assignee3

Accepted answers

Varsha Joshi

Hi @Sujatha Venigalla

Welcome to the community!

I do not think Jira automation has a way to parse the description of an issue and create sub tasks.

All comments

Varsha Joshi

Hi @Sujatha Venigalla

Welcome to the community!

I do not think Jira automation has a way to parse the description of an issue and create sub tasks.

Bill Sheboy

Hi @Sujatha Venigalla -- Welcome to the Atlassian Community!

First, what problem are you trying to solve by typing text into a work item's Description field as if it is a bot / agent to process instructions?

That is, "why do this", rather than just creating the work items?

Next, your post seems to indicate you are using Jira Cloud with an Enterprise license, but you added tags to the question for Jira Data Center and Jira Service Management. When asking questions, I recommend being clear what products and versions you are using.

Kind regards,
Bill

Sujatha Venigalla

ok. Thank you

Sujatha Venigalla

I have not added the tags manually. Removed those defaulted tags.

To reduce manual work to create multiple tasks or sub-tasks for larger projects.

Thanks

Bill Sheboy

I do not believe there is anything built-in to do this. There is no built-in, generic-handle-all-possible-cases parser for field content. And, such a parser would need to identify steps to take when:

the field is updated / cleared,
the created work items are tampered with,
what to do when an Atlassian outage prevents rule executions,
etc.

You could investigate the agents functionality to learn if that might help, although I have not used it.

An alternative is to use a defined format for the field, such as items in bullet points or separated by newlines, and then split the field into a list for iteration to create the work items. That could be done immediately, with no need to add / try new product features.

Sujatha Venigalla

Thank you for the update

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-cloud