> 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/jira-integration.md). # Connect Jira Connect Jira or Jira Service Management to Siit with your Atlassian account, then escalate requests to Jira issues manually or through workflows ### Main use cases * Keep Slack, Microsoft Teams or the Siit Portal as the single place where employees ask for help. * Work on specific requests with teams who use Jira. ### How does the integration work? When a request in Siit is linked to Jira, either manually or through a workflow, Siit creates a Jira issue. Key information then stays in sync between the request and the issue until you unlink them. You decide what syncs in each direction, see [Control what syncs between Siit and your ticketing tool](/guides/integrations/integrations-ticketing/control-what-syncs-between-siit-and-your-ticketing-tool.md). ### How do I connect Jira? Siit connects to Jira and Jira Service Management through Atlassian OAuth. You sign in with your Atlassian account and approve access, so there's no API token to generate. 1. Go to [**Settings → Workspace → Integration library**](https://app.siit.io/settings/integrations/apps). 2. In the **Ticketing** section, find **Jira** or **Jira Service Management** and click **Connect**. 3. Sign in with your Atlassian account. 4. Select the Atlassian site you want to connect, for example `yourcompany.atlassian.net`. 5. Review the permissions Siit asks for and click **Accept**. You're sent back to Siit and the integration shows as active. ### Which Atlassian account should I use? Siit acts with the permissions of the account that connects. Use an account with access to every project you want to escalate to. We recommend a dedicated service account, such as a "Siit Integration" user, so the connection keeps working if an admin leaves. ### What isn't supported? * Issues and requests created directly in Jira don't sync to Siit. Requests always start in Siit. * Advanced Jira formatting doesn't carry over into employee notifications. * If a Jira issue type has required fields, map them in [Custom field mapping](/guides/integrations/integrations-ticketing/custom-field-mapping.md), otherwise escalation fails. The [complete setup guide](/guides/integrations/integrations-ticketing/jira-guide.md) walks you through it. --- # 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/jira-integration.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.