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.

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

Automation between Jira Product Discover (JPD) and Software Project is not working

Cristóbal González
Contributor
March 3, 2025

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:

image.png

image.png

image.png

image.png

 

As you noticing, here in las image says the JSON is valid, nevertheless when the rule is executed, I'm receiving a different message:

 

image.png

Please your help to fix this automation. 

1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2025

Hi @Cristóbal González 

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

Cristóbal González
Contributor
March 3, 2025

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?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2025

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.

Cristóbal González
Contributor
March 3, 2025

Thanks a lot @Bill Sheboy It is working!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events