> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-ticketing.md). # Ticketing Connect Jira, Freshservice and Freshdesk to Siit.
:jira: Connect JiraConnect Jira or Jira Service Management to Siit with your Atlassian account, then escalate requests to Jira issues manually or through workflowsConnect Jira
:atlassian: Connect Jira Service ManagementSet up the Jira or JSM integration end to end: map services to issue types, map mandatory custom fields, configure two-way sync and choose manual or workflow escalationConnect Jira Service Management
:f: Connect FreshserviceEscalate Siit requests to your specialist teams in Freshservice with all the request context carried over and a link kept on both sides.Connect Freshservice
:f: Connect FreshdeskEscalate Siit requests into Freshdesk: the request context comes with it, and a link is kept on both sides.Connect Freshdesk
:rotate: Sync Freshservice messagesWhen a ticket you escalated to Freshservice gets a new reply or note, have it appear automatically on the linked Siit request.Sync Freshservice messages
:toggle-on: Choose what syncs with your ticketing toolChoose what stays in sync between a Siit request and its linked external ticket: resolution status, assignee, internal notes and messages, with separate control over each direction.Choose what syncs with your ticketing tool
:table-columns: Map custom fields for Jira, JSM and ZendeskMap Siit request fields such as status, priority and category to custom fields in Jira, JSM and Zendesk so requests sync or escalate to those tools without losing dataMap custom fields for Jira, JSM and Zendesk
:list-ul: Which Jira fields does Siit use?List the Jira fields the Siit integration uses, such as reporter, summary, issue type, priority and custom fields, and check they are on each issue type screen in JiraWhich Jira fields does Siit use?
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/integrations/integrations-ticketing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.