> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/remediate/jira-remediation.md).

# Jira remediation

Jira Software is an IT service management tool (ITSM) that manages a wide range of development data, including sensitive information, code and user credentials. Unfortunately, most organizations don't have any visibility into the sensitive data stored in Jira.

DoControl provides your organization with a full event log of Jira issues and comments, based on when they were created, updated or deleted. In addition, defining automated workflows can help your organization detect and prevent unnecessary exposure of sensitive data on Jira.

{% hint style="info" %}
To set up Jira remediation actions in workflows, you must be an administrator in the relevant Jira project, and you must have the relevant Jira [Delete permissions](/docontrol-user-guide/integrations/jira-software.md#delete-permissions).
{% endhint %}

## Delete issue

DoControl collects data about Jira issues, including user metadata, comments and attachments.

To prevent exfiltration of sensitive information, such as personally identifiable information (PII), you can define automated workflows with a remediation action to delete the entire Jira issue or selected sub-entities, such as comments and attachments. 

**For example**: If a Jira user in your organization shares a password in an issue comment or attachment, you can receive notification in near real-time and delete the relevant Jira sub-entity.

{% hint style="warning" %}
DoControl deletes Jira issues and sub-entities in near-real time.
{% endhint %}

#### To delete an entire Jira issue or specific sub-entity:

1. In your workflow, define a trigger related to Jira.
2. Add any relevant actions, for example, a conditional action to verify if the Jira issue contains PII, or if it contains an encryption key file from the default keyword list.
3. Add any relevant **Notify** action to send a message to the relevant team.
4. From the Actions pane, select **Remediate > Jira > Delete issue**.
5. For the issue ID, enter the macro for `Get issue ID` or type your own query.
6. Select what you want to delete:
   * Entire Jira issue (including comments and attachments)
   * Selected sub-entities (comments or attachments)
7. If you choose selected sub-entities, enter the relevant **comment ID** or **attachment ID** for each sub-entity. 

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FJqiawU355gytTUCtFKXh%2FJira%20remediation.png?alt=media&amp;token=4f774bf0-feb0-4ebb-b331-f9da733f86c5" alt=""><figcaption><p>Defining a workflow with a remediation action to automatically delete a Jira issue or selected sub-entities</p></figcaption></figure>

{% hint style="warning" %}
After you delete a Jira issue or sub-entity, they are permanently deleted and cannot be recovered.
{% endhint %}


---

# 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.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/remediate/jira-remediation.md?ask=<question>&goal=<user_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.