Custom website form for YouTrack Helpdesk: how to preserve email notifications and reply threading?

Created October 25, 2026 19:10

Hi! We use YouTrack Helpdesk and want to replace the embedded form on our website with our own mobile-friendly UI.

Our backend would submit the customer's name, email, custom fields, and attachments. Customers should not need to sign in.

We need the same behavior as the built-in form: correct reporter assignment, confirmation emails, agents' replies sent by email, and customer email replies added to the same ticket.

What is the currently supported way to implement this?

In a January 2026 forum response, support said POST /api/issues does not populate the Helpdesk channel and may cause notification/threading problems. The suggested workaround was to reproduce the built-in form's undocumented request.

Is this still the case? Is there a supported solution using the REST API, a custom HELPDESK_CHANNEL app, or a workflow that converts an issue into a proper Helpdesk ticket?

Please provide the recommended approach, a working example or documentation link, and the minimum required YouTrack version.

1 comment

Stanislav Dubin

Created October 26, 2026 16:01

Hi Evgeny! There is still no supported way to submit a ticket from a custom UI with exactly the same result as the built-in form, other than reproducing the form's undocumented request, though these limitations can be worked around:

POST /api/issues is the documented way to create an issue. Since build 2026.1.13456 it also sends the "Request Received" email (JT-86113), if it is used to create a helpdesk ticket. However, the reporter has to be an existing user (whereas the form creates the user automatically). This can be worked around if you provide additional automation to create a user before your custom form is submitted.
Customer email replies are matched to a ticket by the ticket ID in the email subject. Tickets from the built-in form have it there, while tickets created through REST use the ticket summary instead, so the first reply may create a new ticket. To avoid this, edit the subject of the reporter notifications in the helpdesk notification templates so that it contains the ID before the summary, for example [Request Received] <#if threadSubject != issue.id>${issue.id}: </#if>${threadSubject}. Apply the same change to the other reporter notification subjects, such as "Ticket Updated". This should let replies land in the original ticket.

Keep in mind that template editing is currently unavailable by default on free YouTrack Cloud instances. If that's your case, please reach out to us directly and we'll enable it.

Regarding the undocumented form request that the forum answer refers to: it's not an official API and can change without notice. If you are on YouTrack Server and choose to rely on this endpoint, it's worth checking whether it functions the same way in a test environment before upgrading your instance.

Please sign in to leave a comment.