Created the below automation to copy a custom field value from Initiative to Epic which is in a hierarchical relationship, on changes to "parent link" field in Epic. The audit log shows as success but the value does not get added to the custom field and instead shows under "original value" and not under "new value" in issue history. Please advise.
Hi @Bharathi
First, in your edit issue action, you are updating the same field twice: once with the field selection (from the dropdown list) and once with JSON. Only one of those may be used at a time.
Next, your JSON update is referencing the smart value {{webhookData}} but the rule makes no calls with Send Web Request.
Kind regards,
Bill
Hi @Bill Sheboy,
Thanks for the inputs. I removed the JSON part and even with the field selection from dropdown, the same thing happens. The JSON referencing the smart value was another try which failed again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the type of the custom field you are trying to copy?
And if it is a multiple-select option field, are you trying to add a value or replace all existing values during the "copy"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Bill Sheboy, It's a single line text field and we are trying to replace the existing value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please post an image of your current, updated rule and the audit log details showing the rule execution. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bharathi
How did you configure the Edit action ?
Also I do not recommend to use JQL condition when possible. Using multiple field condition is more efficient if you can list status instead of using status category.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Florian Bonniec for the prompt response! I can remove the condition to check for statuscategory & issuetype since the rule is configured for create/edit/transition issues only but we need to retain the JQL since fields do not support the check for "parent link" field. Tried multiple options for edit fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On a parallel note, tried the below as well but no luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you try to use {{issue.Parent Link.customfield_10210}} ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just tried this and the same thing happens. The value gets copied but gets dropped somewhere. In the issue history, I see the parent link getting updated and the value for the custom field is available in "original value" and not in "new value"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do not see how to do it using Automation.
I was thinking about getting the value set in a variable using a branch then use the variable to update the field value but it seems that the variable only live within the branch and not within the entire automation rule. Not sure if it's the expected behaviours.
Trigger
For JQL (key = {{issue.Parent Link}})
Create variable X = {{issue.customfield_XXXXX}}
Log Action X
Edit Issue using X
But in this example, log action X will return the expected result but when using it for Edit it's empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Exactly! The value gets copied but doesn't get added and in the end, its empty.
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.