Mario Wijaya

Hello,

I have a question about the Zaf app for ticket editor. I am using ticket.editor.insert to insert a string, which contains markdown/HTML text for the link (e.g., `[hello](https://test.com)`).

The documentation does mention the sanitation and removal of html and/or css. Is there any way to do this so the text `hello` becomes a linkable text rather than a plain text `[hello](https://test.com)`.

For Zendesk api, I could specify the html_body parameter which resolves the issue but I don't see similar functionality for the ZAF app for the ticket editor.

Thanks in advance!

Markdown works perfectly. Thanks!

The API reference that you are referring to is the "Post comment" to a community post and not to a ticket.

I am referring to a customer submitting a ticket through the webform or by other channels and then I would use Zendesk API to surface a private comment on the ticket for our agent's reference.

This is what I am referring to: [Link](https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/)

Does that make sense? Thanks in advance!

Hello,

I am testing adding the private comment to the ticket via Zendesk API. Any documentation on how to add a mixture of text and URL link (via html tag)?

I tried using `>` but it doesn't render as a hyperlink. Any help would be appreciated.

Thanks!

Hi Greg,

Thanks for the information. You are right - I was able to resolve by looking at the required fields to be filled.

Thanks,

Mario

Hello,

I have successfully tested the Zendesk API a few weeks ago (specifically adding the public and/or internal comment as well as solving the ticket).

An example of a request payload will be

{'ticket': {'comment': {'body': '', 'public': True}, 'status': 'solved'}}

Note that this worked perfectly a few weeks ago. Now that I am testing it again - the API works when 'status' element is not passed in (ie. I was able to add a comment but can't solve the ticket regardless of whether there's an assignee or not -- I also tried to solve the ticket without adding a comment and that also failed).

Looking at the request status logs, I am getting a 422 which is weird because this worked flawlessly a few weeks ago. Any idea what could be the issue?

Thanks!