# Jira

{% columns %}
{% column %}
Send Alma findings to Jira as trackable work items.

Triage in Alma first. Then push the outcome to Jira.

Use this when your teams run response from Jira workflows.
{% endcolumn %}

{% column %}
![Jira integration](/files/sQJwhfGM3ad1eXVGNiL7)
{% endcolumn %}
{% endcolumns %}

### What Alma sends to Jira

Alma can create Jira issues from:

* Runtime detections
* Violations
* Incidents

Each issue is enriched with Alma context. That keeps the Jira ticket actionable.

### How it works

1. You connect Alma to your Atlassian account.
2. You approve access in Atlassian consent.
3. Alma can create and update Jira issues.
4. Teams handle assignment and tracking in Jira.

### Prerequisites

* A Jira Cloud site where you can approve app access.
* A Jira project where you want tickets created.
* Alma access with permissions to manage integrations.

### Connect Jira in Alma

In Alma, go to **Integrations** and open **Jira**.

Start the connection wizard. Alma will redirect you to Atlassian to approve access.

### Approve access in Atlassian

You’ll see an Atlassian screen like this:

![Atlassian consent screen](/files/J81raCJ3meTwZYYqHzR9)

Alma requests the following Jira permissions:

* **View**
  * `jira-user`
  * `jira-work`
* **Update**
  * `jira-work`

Click **Accept** to finish the connection.

{% hint style="info" %}
Atlassian grants access to Jira data in places you can access. Only approve this from a trusted admin account.
{% endhint %}

### What the permissions are used for

* `jira-user`
  * Read user identity details needed for routing.
* `jira-work` (View)
  * Read project and issue metadata for creation.
* `jira-work` (Update)
  * Create and update issues created by Alma.

### Verify the integration

* Create a test finding in Alma, if available.
* Confirm a new Jira issue appears in the target project.
* Open the issue and verify it links back to Alma.

### Disconnect / revoke

* In Alma, disconnect the Jira integration.
* In Atlassian, remove Alma Security from connected apps.

### Troubleshooting

* **Can’t complete Atlassian consent**
  * Confirm you’re an org/site admin (or have approval rights).
  * Check whether your org blocks new marketplace apps.
* **Issues don’t appear in the expected project**
  * Re-check the project selected during setup.
  * Confirm your Jira permissions allow issue creation in that project.


---

# 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.alma-security.com/integrations/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.