# Remediate via Jira

Create Jira tickets directly from Veza dashboards and queries to assign remediation work. Each ticket includes the finding title, a direct link back to Veza, and any notes you provide.

## Prerequisites

Before remediating via Jira:

* A [Jira Veza Action](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md) is configured in **Integrations** > **Veza Actions**
* Your account has the required [remediation permissions](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions.md#required-permissions)

## Remediate from a dashboard

![Remediate button and dropdown on the dashboard toolbar](/files/Iosnp8exCIFf9mOhbCRQ)

1. Navigate to **Access Intelligence** > **Dashboards**.
2. Open the dashboard.
3. Click **Remediate** in the dashboard actions toolbar.
4. Select **Create Jira Ticket** from the dropdown.

   ![Jira remediation modal showing Veza Action selector, Assign To, Notes, and live preview](/files/LRHBMjpgEdScwgYqEshL)
5. In the modal dialog:
   * Select one or more **Veza Actions** to use as the delivery destination. Each selected action creates a separate Jira ticket.
   * Optionally select an **Assign To** team member (see [Jira assignee](#jira-assignee) below).
   * Add optional **Notes** to provide context for the remediation.
6. Review the live preview showing the Jira ticket content.
7. Click **Create** to submit.

## Remediate from query details

![Remediate button on the query details toolbar](/files/5Mc56SyyYUJclOMVIhPP)

1. Open a saved query from **Access Intelligence** > **Saved Queries**.
2. Click **Remediate** in the query details toolbar.
3. Select **Create Jira Ticket** from the dropdown.
4. Complete the form as described above.

The workflow is identical to dashboard remediation, but the generated ticket references the specific query instead of the dashboard.

## Jira ticket format

Jira tickets use a unified human-readable format with Jira markup. The title follows the pattern `[Veza Action] <Severity>: <Query Name>`, and the ticket body follows this structure:

```txt
The query "AWS IAM Roles with S3 update permissions" returned 12 results.

Severity: Medium
Triggered By: Jane Smith
Triggered Time: Apr 17, 2026, 2:21:00 PM UTC
Query Name: AWS IAM Roles with S3 update permissions
Query Source: AwsIamRole
Query Destination: S3Bucket
Query Link: [AWS IAM Roles with S3 update permissions|https://your-tenant.veza.cloud/app/assessments/f300f690-91c9-4bfd-bd71-eeb399fdce82]
Notes: Please review and remove unused permissions by end of sprint.

Please note that you must authenticate to the Veza platform to access the link. If you have any trouble accessing the link, please contact your Veza administrator.
```

For dashboard remediation, the severity line is omitted and the message references the dashboard name and URL instead.

## Jira assignee

When remediating via Jira, you can optionally assign the ticket to a specific team member. The **Assign To** dropdown lists all Veza users by name and email. The selected user's email address is passed to the Jira API to set the ticket assignee.

If no assignee is selected, the ticket uses the default assignee configured in the Jira Veza Action (if one is set).

For additional Jira notification format details and examples, see [Jira Veza Action: Example notifications](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md#example-notifications).

## See also

* [Remediation actions](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions.md) (overview, permissions, and troubleshooting)
* [Remediate via ServiceNow](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-servicenow.md)
* [Remediate via Slack](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-slack.md)
* [Jira Veza Action](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md) (setup and configuration)


---

# 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.veza.com/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-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.