invalid json in automation for jira

David Wuth

I am trying to edit the Advanced Roadmap TEAM field. I can use the following without error as a LOG action: 

Parent team {{triggerissue.customfield_13100}}, story team {{issue.customfield_13100}}

 

But, when I try to set a field value (I want to copy the value of the custom field in the trigger issue), I get a "not valid json" error.

{ "fields":
   { "customfield_13100": {{triggerissue.fields.customfield_13100.value}}
   }
}

 

When I add quotes around the trigger issue, then I get an error that the field does not exist.

{ "fields":
   { "customfield_13100": " {{triggerissue.fields.customfield_13100.value}} "
   }
}

I cannot use the standard edit issue and select the field because the Team field from Advanced Roadmaps is not available. Remember, there are TWO Team fields in Jira now, if you use Advanced Roadmaps.

 

Bill Sheboy

Hi @David Wuth 

I have not edited fields in the automation rules using JSON yet... I did look over the documentation and I wonder if there is an issue with how the automation is parsing within the quotation marks for the fields: https://support.atlassian.com/jira-core-cloud/docs/advanced-field-editing-json/

I saw one posting that used a method similar to you, but did not have the extra spaces within the quoted value:

{ "fields":
   { "customfield_13100": "{{triggerIssue.fields.customfield_13100.value}}"
   }
}

The documentation also shows examples using the function asJsonString, maybe something like this:

{ "fields":
   { "customfield_13100": {{triggerIssue.fields.customfield_13100.asJsonString}}
   }
}

Maybe try those to see if they help.

 

Best regards,

Bill