---
title: "Quick fix"
canonical: "https://support.appfire.com/space/IC/198508665/Quick%20fix"
format: markdown
---
> Macro (aura-html)

## What is a quick fix action?

Integrity Check for Jira provides quick, predefined actions to automatically fix common configuration problems with a single click. These are what we call quick fix** **actions. With just a simple button press,** **they allow you to address detected problems without leaving the app.

## How it works

The quick fix actions are located in the *Details* section of each detected problem. After the violation check finishes, you can expand any violation with the arrow (:arrow_left:) button. After that, you can use the dedicated action button (i.e. *Delete*, *Update*) in the *Location*** **section of an error to resolve the specific configuration problem.

![image](media://514d2174-3df0-4f0f-abcd-76b1dca82720)

[Configuration Manager for Jira](https://appfire.atlassian.net/wiki/spaces/CMJ) needs to be installed with a valid license if you want to use the quick fix actions. Otherwise, the actions are disabled, and a message pops up indicating that a valid license is needed.

![image](media://f7c65463-5295-4077-b56d-78e535692bd6)

## Bulk quick fix

You can also use the **Quick fix** button to automatically resolve all configuration errors with available quick fixes. The button is located at the top of the violation list and has a counter showing the sum of available quick fixes.

With this action, you can apply all available quick fixes to your configuration with a single click. After confirming the changes, all available quick fixes are applied to your Jira one after another.

![image](media://ccbf4c73-affe-4fe6-a94b-3689a2947a84)

## List of quick fix actions

Here, you can learn which configuration problems have quick fix actions in Integrity Check for Jira.

| **Problem** | **Action** |
| --- | --- |
| Agile board referring to a missing filter<br>Example: *Agile Board Scrum board refers to the missing filter 10000.* | Deletes the board. |
| Project role is referring to a missing user<br>Example:* Project 'TestProject' refers to the missing user testUser.* | Removes the user role actor from the project role. The project role will still be visible in the path. |
| Project role is referring to a missing group<br>Example:* Project 'TestProject' refers to the missing group testGroup.* | Removes the group role actor from the project role. The project role will still be visible in the path. |
| Dashboard gadget referring to a missing custom field or sprint | Deletes reference to the missing field or sprint. |
| Dashboard gadget referring to a missing object (breaking the gadget) | Deletes the gadget. |
| Agile board referring to a missing field from the detail view | Deletes reference to the missing field. |
| Agile board referring to a missing field from the card layout | Deletes reference to the missing field. |
| JSM queue column referring to a missing field | Deletes reference to the missing field. |
| JSM request type referring to a missing custom field | Deletes reference to the missing field. |
| Dashboard or filter referring to missing group/user permissions | Deletes the reference to the missing group or user permissions. |
| Filters with invalid JQLs | Changes the JQL to:   
*"createdDate Is EMPTY and text ~ ‘Original query: ........ ' ". *<br>The *Original query* part contains the filter's original JQL. This way, the filter won’t cause any errors or warnings, and the user can fix it after deployment. Use [Power Admin](https://appfire.atlassian.net/wiki/spaces/PA) to easily find the changed JQLs (e.g. search for all filters that contain the text “Original query”). |