# Jira

## Overview

The Jira integration brings Sola AI into your Jira projects allowing you to create, update, and track Jira issues directly from in-chat conversations. 

The Jira integration helps streamline remediation management by turning your security findings into actionable work, keeping teams aligned and responsive.

With the Jira integration, you can:

* Turn security findings into Jira epics, tasks, or stories directly from Sola AI conversations.
* Route issues to the right stakeholders with relevant context for resolution.
* Monitor issue status, transitions, and comments, from detection to closure.

{% hint style="warning" %}
**Sola can only perform the actions you approve.**

Connectors require explicit permission to access or act on external systems. Permissions are securely managed at the workspace, app, and chat level to ensure control at every step.
{% endhint %}

## Set up Jira connector integration with Sola

{% columns %}
{% column width="75%" %}
Go to ***Integrations*** > [***Connectors***](https://app.sola.security/integrations/connectors) > click ***New connector*** > select ***Jira***.

*The Sola wizard will take you through the steps.*
{% endcolumn %}

{% column width="25%" %} <a href="https://app.sola.security/integrations/connectors?connector=jira" class="button primary">Set up Jira -></a>

{% endcolumn %}
{% endcolumns %}

### Connect Jira to Sola

{% hint style="warning" %}
To connect Jira, it is recommended to use a **dedicated organization user account**, for the Sola connector, and not a personal account. For example, *<sola.jira.user@company.com>*.
{% endhint %}

{% tabs %}
{% tab title="Jira App" %}
Recommended for secure, production use.\
This method uses a Jira App to grant Sola scoped, permission-based access to your Jira account.

* Jira App (Recommended)\
  Install Sola’s Jira App to securely and easily grant access to your organization’s Jira account.
  {% endtab %}

{% tab title="API Token" %}
This method uses a Jira API token to securely grant Sola access to your Jira account.

The token includes the following classic scopes:

* `read:jira-user`
* `read:jira-work`
* `write:jira-work`
  {% endtab %}
  {% endtabs %}

## Available actions with the Jira connector

* **Create issue** - Create a new Jira issue (Task, Bug, Story, Epic, etc.) with summary, description, assignee, components, and custom fields.
* **Update issue** - Update an existing Jira issue summary, description, priority, assignee, or labels.
* **Get issue** - Retrieve detailed information about a specific Jira issue by its key.
* **Get projects** - List all accessible Jira projects.
* **Get issue types** - List available issue types (Task, Bug, Story, Epic, etc.) for a specific project.
* **Add comment** - Add a comment to an existing Jira issue.
* **Get comments** - Retrieve comments for a specific Jira issue.
* **Transition issue** - Change the status of a Jira issue (e.g., move to In Progress, Done, Closed) using a transition ID.
* **Get transitions** - List all possible status transitions for a Jira issue.
* **Search fields** - Search for available fields in the Jira instance (e.g., custom fields).
* **Create issue link** - Link two Jira issues together (e.g., “relates to”, “blocks”, etc.).
* **Link to epic** - Link an issue to an Epic.
* **Batch create issues** - Create multiple Jira issues in a single batch operation.
* **Get link types** - List all available Jira issue link types.
* **Get project issues** - List issues for a specific Jira project.
* **Search issues** - Search for Jira issues using JQL (Jira Query Language).
* **Get user profile** - Retrieve a Jira user’s profile by identifier (accountId, username, or email).


---

# Agent Instructions: 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:

```
GET https://docs.sola.security/integrations/connectors/jira.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.