In July 2020, Zendesk made changes to how the assignee ticket field values are loaded. Previously, all assignee options were available immediately. Now, these values are lazily loaded, meaning they only become available when an agent clicks on the assignee ticket field. This change requires apps to listen for theticketFields.assignee.optionValues.changed
event to ensure they have the latest options.
Additionally, when calling.get(ticketFields:assignee.options)
, the output now includes avalue
property formatted asgroupId:groupId
for nested group options. This update does not affect the.get('ticket.assignee')
method, which still returns the current assignee value. For more details, you can refer to theoriginal Zendesk article.
To ensure your app receives updated assignee options, it must listen for theticketFields.assignee.optionValues.changed
event. This event triggers whenever new options are loaded into the agent interface, allowing your app to call the.get()
…
No, the change to ZAF ticketFields does not affect the current assignee value. The.get('ticket.assignee')
method will continue to return the currently saved value for the ticket’s assignee, unaffected by the July 2020 update. The update…
Developers should ensure their apps are set up to listen for theticketFields.assignee.optionValues.changed
event. This is crucial for apps to receive updated assignee options as they are lazily loaded into the agent interface. Additionally,…
To test the new version of the assignee ticket field, you need to submit the Zendesk subdomain of the account you want the changes enabled on. Once submitted, Zendesk will reach out when your access has been provisioned. This allows you to test…