Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I check if a certain sub-task exists yet using Automation for JIRA?

andreas Community Leader Sep 20, 2016

I want to write an Automation rule that only adds sub-tasks if that sub-task doesn't exist yet on an issue.  Is this possible with Automation for JIRA?

1 answer

1 accepted

1 vote
Answer accepted
andreas Community Leader Sep 20, 2016

Once again the compare condition (see all our rule components) can help here with smart-values:

Project automation - Code Barrel JIRA 2016-09-21 10-16-13.png

So this rule uses the compare condition to create a string out of all existing subtask summaries. If no subtasks exist yet, then it will simply be the empty string. However otherwise it will concatenate all existing subtask summaries separated by a space character.  We then check using a regular expression if this string contains the subtask summary of the new subtask we want to create yet ("my awesome subtask") in this case.

Only if the existing subtask summaries don't match this string yet (i.e. it doesn't exist), will the rule continue and create our 1 sub-task with the summary "my awesome subtask".

The extra space inside this smart-value completion is important (it separates the subtask summaries by a space if there's multiple subtasks):

{{#issue.fields.subtasks}}{{fields.summary}} {{/issue.fields.subtasks}}
andreas Community Leader Sep 20, 2016

You can also compare other sub-task attributes, by using something other than fields.summary in the example above. For example:

How can I check if an issue already exists in an epic?

This works if the trigger issue is not an epic and has an epic link.existsInEpic.PNG

Like Paul Benati likes this

Thanks for this answer as it worked like a champ for my use case!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

182 views 3 19
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you