JSON in Jira Automation for Custom User Field = Assignee

[Bryan Fitzgerald]

Hi all!

I'm looking to write an automation rule for the following:

1) In the child task, Content Design, the Assignee is changed

2) In it's parent Epic, the custom field Content LED is changed to the same user.

I'm running into issues, first because Jira does not recognize the custom Content LED field as one that can be selected in the standard drop down. From searching, I see it's likely due to it being a user ID field, which is fine as long as I can do it with the advanced functionality.

Second, I have never written a rule in JSON before and don't have much of an idea to what I'm doing. I've tried to look at examples, including a few from the community here, but still can't get it to run successfully. 

Screenshot below of where I'm at. The warning message I'm getting says the JSON is valid, but that it can't be validated until the rule is run. Whenever I run the rule, I get a message that the JSON is invalid.

Any help at all is much appreciated!

[Calvin]

Hi mate, do you know if its in the "parent" Screen and if its in the Project context. I only ask because I created a "Content LED" field of user picker type and I can choose it in the dropdown

In anycase your advanced field is almost perfect, you just need to put the triggerIssue.assignee part in quotes:

[Marc - Devoteam]

Hi @Bryan Fitzgerald and @Calvin 

Correct on the trigger isuse assignee point.

But Custom LED is a field in Jira this needs to be defined as "issue.Custom LED", but most of the times this will even fail and you need to provide the custom field ID, like;

"issue.customfield_xxxxx", where xxxxx is the id number of the field.

[YY Brother]

Hi @Bryan Fitzgerald 

Welcome to our community.

Maybe you could have a try:
1.create a variable and store the changed assignee in it

2.In the Branch, just use edit work item action and set parent's assignee as that variable

Hope it helps.

YY Brother