chat-core-zendesk: add support for ticketFields #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds support for the new ticketFields param on the ZendeskHandoff returned from the Chat API. This allows fields specified in the bot config to autopopulate in arbitrary custom Zendesk fields. TEST=manual,auto Ran test site locally, using a bot with a field's ID set in the ticketFields. Initiated a support session, saw the field populated with the specified value. Wrote a unit test validating that the parameters are used and formatted correctly, saw it pass.
nbramblett
reviewed
Sep 19, 2024
nbramblett
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for the new ticketFields param on the ZendeskHandoff returned from the Chat API. This allows fields specified in the bot config to autopopulate in arbitrary custom Zendesk fields.
TEST=manual,auto
Ran test site locally, using a bot with a field's ID set in the ticketFields. Initiated a support session, saw the field populated with the specified value.
Wrote a unit test validating that the parameters are used and formatted correctly, saw it pass.