> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/integrations-automations-and-workflows/integration-guides/external-issue-and-ticketing-systems/how-to-create-tickets-from-suptask-to-jira.md).

# Create tickets from Suptask to JIRA

{% hint style="danger" %}
This is a deprecated document which have been replaced by the [new JIRA integration](/integrations-automations-and-workflows/integration-guides/jira-software.md).
{% endhint %}

### Overview

The Suptask integration with JIRA (e.g JIRA software) enables you to escalate tickets directly from Slack to JIRA. With a single reaction emoji (the 🌪️ :tornado:) you'll be able to create tickets to your choice of repositories, directly from a Suptask ticket in Slack. 

{% hint style="info" %}
Contact [Suptask Support](/getting-started/contact-support.md) to get access and help you set up the JIRA integration in Suptask.
{% endhint %}

***

### **Prerequisites**

1. Create an API token for your user account in JIRA.(<https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)\\>
   \
   Store the token once you have it. You will need it when configuring the integration within Suptask.&#x20;
2. The JIRA Project ID (e.g *10000*) of the Project where you want tickets to be created in.\
   Read more: <https://confluence.atlassian.com/jirakb/how-to-get-project-id-from-the-jira-user-interface-827341414.html&#x20>;
3. The issue type ID (e.g *10001*) which should be used when creating the issue in JIRA\
   Read more: <https://confluence.atlassian.com/jirasoftwarecloud/finding-the-issue-type-id-in-jira-cloud-1333825937.html>
4. The email of your JIRA/Atlassian user account e.g *<first.lastname@acme.com>*&#x20;
5. The URL of your JIRA Software instance e.g *<https://myacme.atlassian.net>*

***

### **Use the JIRA integration with Suptask**

* Make sure you are within the **Responder channel** of the **Inbox**.&#x20;
* On one of the received tickets in the channel, add the (the 🌪️ :tornado:) **reaction emoji** to the ticket message in the channel. See below for sample screenshot.&#x20;
* This will trigger a selection where you can specify to what **integration target** you want to **send the new ticket to**.&#x20;
* Use the **placeholders** to add in Suptask ticket information. Especially the ticketUrl placeholder is valuable as it takes you directly to the Suptask ticket in Slack as a reference.\
  These placeholders include the Suptask ticket link, description, fields, ID etc.&#x20;

Example screenshot on adding the tornado to a ticket message in the Agent Responder channel:

<figure><img src="/files/EeJdfGvkoiex2nfxxqlk" alt=""><figcaption></figcaption></figure>

After creating a related ticket in JIRA, the ticket message thread in Slack will receive the JIRA issue url, linking the both tickets together.&#x20;

<figure><img src="/files/bcDCBxY9OkG123IsIXeh" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.suptask.com/integrations-automations-and-workflows/integration-guides/external-issue-and-ticketing-systems/how-to-create-tickets-from-suptask-to-jira.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.