Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to avoid Auto sub-task creation if subtask in parent with same summary already exists?

I have set up auto-sub task creation using post functions on a  transitions in our workflow. However,  it works fine in creating auto sub-task when i use that transition. But i don't want them to be recreated if this process has to be repeated. I am using scriptrunner built in script for auto-creating subtask on transition.

I want to create a condition for avoiding the creation for the post function feature 'create subtask' if a subtask with the same summary already exists.

Thanks in advance,


1 answer

1 accepted

1 vote
Answer accepted

I got the Script here it is

I"ve added the below script into the create a sub-task post function code editor condition. You'd need to update 'manage onboarding' to be the relevant summary of the sub task that you don't want to re-create if the same summary exists. 

import com.atlassian.jira.component.ComponentAccessor


def subtasks = issue.subTaskObjects

if(subtasks.find{it.summary == "Manage Onboarding"})


    return false




    return true


Hi @siva , how to change the condition to the issue type name instead of the summary of the sub-task?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events