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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,414,268
Community Members
 
Community Events
170
Community Groups

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.

4 answers

1 accepted

7 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

Thanks! Exactly what I needed!

2 votes

@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

Hi @DS,

I am Marlene from codefortynine.

We've just released an update for our Marketplace app Advanced Bulk Edit for Jira that enables you to remove text from the issue summary in bulk. Our app is easy to use and would fit if Jira users have to remove text from issue summaries on a regular basis.

  • Navigate to the advanced issue search
  • Filter for the issues you want to bulk edit
  • Click "Bulk Edit" button
  • Add "summary" as the field you want to edit
  • Select "replace with"
  • Enter Replace "Clone-" with (leave blank)

advanced-bulk-edit-jira_remove-from-summary.png

If you have questions or feedback about Advanced Bulk Edit for Jira, don't hesitate to contact us.

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

Atlassian Community Events