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"
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.