Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.
×Hi!
I created an automation to update a Custom Field when a JPD field (Launch Tier) is updated but it is not working.
Here how I created:
As you noticing, here in las image says the JSON is valid, nevertheless when the rule is executed, I'm receiving a different message:
Please your help to fix this automation.
That error is correct as the {{fieldChange}} smart value likely creates the invalid JSON. You could confirm this by writing the smart value to the audit log and considering what that would do to the JSON expression shown.
What is the type of your customfield_17300 in the software project and what value are you trying to use as the source from the JPD idea's Launch Tier field?
For example, if the destination field is a single-select, option field, could the rule just save the current value from the trigger issue?
{
"fields" : {
"customfield_17300": {
"value": "{{triggerIssue.LaunchTierCustomFieldID.value}}"
}
}
}
Kind regards,
Bill
Hi @Bill Sheboy Thanks a lot for your quick reply!
The type of the customfield_17300 is single-select as well as the JPD field (source), and what I'm trying to set in the customfield_17300 is the same value from JPD field, the Launch Tier value that has just set or modified to.
{
"fields" : {
"customfield_17300": {
"value": "{{triggerIssue.LaunchTierCustomField_17213.value}}"
}
}
}
If I change the "{{triggerIssue.LaunchTierCustomFieldID.value}}" for "{{triggerIssue.LaunchTierCustomField_17213.value}}" where Customfield_17213 is the JPD Field Launch Tier is the correct way?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I put as LaunchTierCustomFieldID was a placeholder. Please replace that with your field: customfield_17213
Please note the values must exactly match, including case-sensitivity, for this to work.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.