Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automated tasks creation with sub-tasks

Yahya Aliyev November 17, 2025

Dear Community,

I came across a small issue. 

Basically, I need a rule to create two different issues with sub-tasks populated within each.

However, my rule duplicates subtasks in each created Story.

How to prevent this duplication, so the rule will create exact subtasks under the exact Story.

Here is the screen.Screenshot 2025-11-17 at 13.51.53.png

4 answers

1 accepted

1 vote
Answer accepted
Yahya Aliyev November 17, 2025

Dear Community,

 

Thank you for the prompt replies. I've found the solution to the issue. The problem with the "Most recently created work item" is that there are 2 Stories created at the same time, and this branch condition counts both of them, thus validating both for the subtask creation, which ends up with duplicates.

 

I came up with another solution, which is an additional IF condition.

During the creation of the Story, I populate the Description field with a unique value. Then I do the validation based on the content for this unique value.

This works best for this case.

Screenshot 2025-11-17 at 15.07.52.png

2 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 17, 2025

Hi @Yahya Aliyev

Thanks for the question.

Your rule is creating duplicate subtasks because each branch is iterating over multiple issues. In your case, both “For: Current issue” and “For: Children” branches are causing the automation to re-run the “Create Sub-task” action for each created Story, which results in the same sub-tasks being added more than once.

For the solution, do this.

 

Trigger - Manual Trigger

Action - Create Story A

Branch - Most Recently Created Issue

  • Action: Create Sub-task 1

  • Action: Create Sub-task 2

And for the Parent field, use {{createdIssue.key}}.

And the same for the second block.

See the attached screenshot.



Screenshot 2025-11-17 143229.png

Tudor Tofan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 17, 2025

You can simply go with the predefined "current work item" option in the "Parent work item field".
Of course, your suggestion is achieving the same result, but it's much more advanced for a person who is new to Jira Automation, 

Screenshot 2025-11-17 124901.png

 

Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 17, 2025

Dear @Tudor Tofan

Yes, thanks, it is also working one.
I provide an advanced version, to become advanced :)

0 votes
Tudor Tofan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 17, 2025

Hi @Yahya Aliyev !

Your automation should look like this

Screenshot 2025-11-17 124524.png

 

If this solves your issue, please accept my answer

0 votes
Vishnu Vardhan November 17, 2025

Hi @Yahya Aliyev 

Good day!

Can you clarify if that story is also created automatically when you trigger the automation rule manually?

 

Regards,

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events