Automation - How to update a custom field from a value in a linked issue 's custom field

[James Meyer-Bejdl]

Could someone work out what I've done wrong here. I have an automation which should transition a linked issue when the trigger issue is resolved and update a custom field on the linked issue based on the value in a custom field on the trigger issue. The transition works absolutely fine but the value in the custom field never gets set. I think it must be to do with the branch but I thought {{triggerIssue.customfield_XXX}} should have access to the trigger issues field even within the branch. For clarity when this automation runs, the linked issue is transitioned correctly and the automation runs without error but the custom field value in the linked issue remains empty. Any help would be gratefully received. I have absolutely no idea what I've done wrong. Here's a screenshot of the relevant part of the automation: 

[Austin C_ · Accepted solution]

@James Meyer-Bejdl 
What is the custom field type you are updating?

I have found in certain cases, if your custom field is a dropdown, radio button, or user picker, just using {{triggerIssue.customfield_xxx}} might return a complex object. Try adding .value or .name (e.g., {{triggerIssue.customfield_xxx.value}}) to extract the actual text.

Another possible solution I found in a thread: 
You may need to add a refetch data. If the trigger issue's custom field value was set during the resolution transition (e.g., on a transition screen), the automation might trigger before Jira has finished updating the database. Adding a refetch issue action at the start of your branch rule ensures the automation sees the most current data.

[James Meyer-Bejdl]

Both fields are simple text. I'll try fetching the issue at the beginning of the branch. Certainly worth a try. The value was definitely not changed during the transition but given how strangely branches seem to work, I can believe I might have to get the details anyway.

[James Meyer-Bejdl]

That seems to have worked. I just don't understand why

[Austin C_]

It's hard to know because we don't have access to the Jira db in cloud, but you could do some fun testing with Postman to see how long it takes your db to update values. Using Postman echos or Postman delay blocks could give you a good start to your investigation.

Jira db documentation says Jira updates the existing record for that specific issue in the jiraissue table (e.g., resolution column updated from <null> -> Fixed or Done) and not re-added. One would think the data would still be available during the automation.

Glad that worked though, have a great day!

[Aaron Pavez _ServiceRocket_]

Hi @James Meyer-Bejdl 

What type of field are you using?  a text field? picklist?multipicklist?user?

Regards

[James Meyer-Bejdl]

Sorry, should have said. Both custom fields are simple text fields