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):
Hi I am new to Jira automation and this forum. So please forgive me.
Can you show how you have used this in an example please. My first delve into adding Automation to our Jira is to have approval and estimation tickets created. I am using the transition to review as trigger. I wan to ensure that if the status is reset, that the tasks are not created again.
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...