nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Replace CLONE with in summary with customer name field

Mayuresh T Athalekar

Here is the workflow that i am trying to implement both for issues already created and those getting created new.

1. I have a work item (story) holder with all required subtasks and other details created. One of the issues field is customer name.

2. I am cloning the user story to create a another work scope where it also clones the sub-tasks.

3. Here, the issue is it adds a CLONE work prefix to each sub-task.

4. I could resolve removing the CLONE word using an automation rule, however, i am curious if there is a way to add "Customer name" as prefix POST creating the cloned issues as i will be filling the customer name later.

So essentially, i will be needing the rule to add a "Customer name" prefix to the cloned work item.

In such a case, I can disable the automation rule, which only removes the CLONE word from the summary. With the enhanced rule, I will remove CLONE work and replace it with "Customer name"

Accepted answers

All comments

Marc -Devoteam-

Hi @Mayuresh T Athalekar

Welcome to the community.

You could use a lookup table in in an automation rule and based on a custom field that matches the value in the lookup table you could then use this as variable to plac in the summary when cloning.

Bert Dombrecht

Hi Mayuresh,

How are you cloning the work item?
- Manually?
- Workflow post-function (ScriptRunner)?
- Automation?

With Automation, you can set the summary of a cloned work item directly with smart values as:

{{issue.customfield_123}} - {{issue.summary}}

Where you replace customfield_123 with the id of your customer name field.

Or get the custom field value from the parent with:

{{issue.parent.customfield_123}}

Or get the summary without "CLONE" with:

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

Does this help?

Mayuresh T Athalekar

I am manually doing cloning and a rule is currently set to remove CLONE work from summary.

What i am looking for is to remove the clone word and append {CustomerName} in the summary.

Now here issue is - I have a group of tasks created under a story which is my dummy bucket of work. Certain values changes like customer name when by cloning the bucket for creating bunch of tasks for another customer. The customer name is replaced once the bucket is created by clone process. So far so good as CLONE removal rule is removing the CLONE work from summary.

Now i will add "Customer Name" which is a custom field dropdown and my ask is to append this name on every child item (sub-task) as soon as i select the customer name at story level.

Bert Dombrecht

If I understand correctly, you'd then need to create an automation rule with:

Trigger: Field Value Changed ("Customer Name")

Condition: perhaps any condition that rules out unwanted updates (Customer Name is not blank, work type is story, ...)

Branch: For sub-tasks

Action: update summary (using smart values as documented above)

Here's an example, using the components field.
You can replace this with your custom field. You can also make it more robust in case the field is updated multiple times...

Mayuresh T Athalekar

Interesting, Let me give a try if it works ! Thank you @Bert Dombrecht

Luka Hummel - codefortynine

Hi @Mayuresh T Athalekar

With our Deep Clone for Jira, you can swap the default “CLONE –” prefix for the value of your Customer name field while you clone:

When cloning with Deep Clone, you can disable the prefix option, so no prefix is set.

2025-05-12 14-51.png

Then you can use the Field Editor feature with a Jira expression like this

issue.customfield_12345 + " " + issue.summary

The clone will be created with the customer’s name at the front instead of “CLONE –”.

Need this to run automatically? Add a Deep Clone Post Function to the appropriate transition and select the preset—keeping your workflow clean and completely no-code.

Bill Sheboy

Hi @Luka Hummel - codefortynine

As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information about this, please see:

Atlassian Partners - Rules of Engagement

https://community.atlassian.com/t5/App-Central-articles/Atlassian-Partners-Rules-of-Engagement/ba-p/2899328

Kind regards,
Bill

Clara Belin-Brosseau_Elevatic

Hi @Mayuresh T Athalekar

As an alternative to Automation that can be really complex to implement sometimes, I can suggest trying our app Elements Copy & Sync to clone Jira issues, subtasks and automatically modify their summary.

Don't hesitate to check the documentation, it’s really quick and easy to set up.

The app is for free during 30 days (and it stays free under 10 users).

Mayuresh T Athalekar

For now i have applied the automation rule to remove the CLONE from the summary. To keep it simple, the person who is going to clone the parent story will have to add the customer name now. This is based on use cases that i came across while implementing the rule based solution which works for us now for last 2+ weeks without any complaints from anyone.

additionally, i have also incorporated separate rule to remove the clone links, so the newly cloned ticket will not have unwanted links created out of clone process.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud