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

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

Need to remove "Clone-" prefix from many subtasks

I recently created many clones of stories and now all of my cloned subtasks say "Clone-" as a prefix to the subtask. Is there any way to remove this prefix from all the subtasks at once? Right now im going through and deleting the prefix manually but I have hundreds of subtasks that this needs to be done too.

3 answers

1 accepted

3 votes
Answer accepted

Hi @DS -- Welcome to the Atlassian Community!

You may do this with an automation for Jira (A4J) rule to remove that prefix.  Your project admin will need to create the rule.  Here is an example of such a rule:

  • Trigger: scheduled for JQL of: summary ~ "CLONE"
  • Action: edit issue fields for summary, setting the value to {{issue.summary.substringAfter("CLONE - ")}}

I recommend validating this rule in a test project to see that it does what you wish first, and then add it to your project.

Automation rules can only process up to 100 issues at a time, so I selected a scheduled trigger as that can be run repeatedly, manually.  Once you have processed all of the issues, you may disable the rule.

To learn more about automation rules, please look here:

Best regards,

Bill

Thanks Bill, that definitely seems like the best way to go about this. However, when I tried to create a rule it seems to fail with the error of:

"Action details:

Edit Issue

Error editing issuesDIL-5 (You must specify a summary of the issue. (summary)), DIL-6 (You must specify a summary of the issue. (summary)), DIL-3 (You must specify a summary of the issue. (summary)), DIL-7 (You must specify a summary of the issue. (summary)), DIL-4 (You must specify a summary of the issue. (summary))"

 

Do you know what I'm doing wrong here? Your help is greatly appreciated!Project automation - Jira 2021-06-22 14-52-33.pngProject automation - Jira 2021-06-22 14-53-27.png

That is curious... That seems to behave as if issues are being found without "CLONE", and/or issues are being processed multiple times, and/or there is a timing issue.

Would you please post an image of your complete rule and of an execution from the audit log?

After that, please try to write the modified summary to the audit log rather than editing the issue.  That may help reveal what is happening.

Thanks!

Actually, after testing your example on the main project im working on, It seems to have worked perfectly . However, in my test project environment, i had to use this value:

{{issue.summary.substringAfter("CLONE - ")}} {{issue.summary.substringAfter("- ")}}

in the edit issue Summary field to get it working. Not sure if i set something up wrong in my test environment but all is working now. Thanks for your help!

Like Bill Sheboy likes this

@DS 

Welcome to the community.

You could do that with an Automation rule that uses a manual trigger.

Action would be Edit Issue Field. You could use Advanced Edit with JSON and smart values to reset the value of the field to its string minus the "Clone-" text.

References:

https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/

https://support.atlassian.com/jira-software-cloud/docs/smart-values-text-fields/

Hi, Trudy!

I suggested a scheduled rather than a manual trigger for this rule (when using JQL for a batch) as manual rules auto-magically exclude the trigger issue key from the JQL behind the scenes.  Same thing for branch JQL.  I believe this was done to prevent race-track errors.

Best regards,

Bill

Like Trudy Claspill likes this
0 votes
Mirek Community Leader Jun 18, 2021

Hi @DS ,

Not sure if you are a site admin or not. I think that it can be done by using CSV export import. I mean search and then export impacted issues, modify the summary values and then Import that CSV file but making sure that you have correct mapping to modify the existing issues not create new one!

See "Updating existing issues" in

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

733 views 2 21
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