Creating global automation for removing CLONE from sub-tasks

Question

I am looking to create automation for when a standard issue with sub-tasks is clone so CLONE is automatically removed from the Summary of all sub-tasks.

I tried to use AI for this, but it wasn't quite correct.  It would remove from 1 or 2 sub-tasks, but not all.

Bill Sheboy · Answer

Awesome; I am glad to learn that helped!

FYI...I recommended that simple rule approach as you appear to be on the Premium license level, and so have more automation usage executions per month: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits

And so that rule will count one usage for every issue created.  If that becomes a problem, you may modify the rule to add a condition before the edit:

* smart value condition:* first value: {{issue.summary.left(7)}}
* condition: equals
* second value: CLONE -

With that in place, the rule will only "count" for usage if the condition is met and the edit occurs.

Tara Bell · Answer

@Bill Sheboy - this did the trick! Thanks so much!

Bill Sheboy · Answer

Hi @Tara Bell

To remove the "CLONE - " prefix from the issues, you could use a rule triggered on Issue Created, and the grab the text after that.  However...an observant person may remove the prefix when the issue is created, and so try a technique that will only remove() the value when found: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#remove-String-remove-

For example:

* trigger: Issue Created
* action: Re-fetch Issue (This is to reload the data before the rule proceeds, preventing any timing problems with the issue created trigger.)
* action: edit issue, setting the Summary field to

Kind regards,
Bill