> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/risk-management/monitor-and-manage-code-build/fix-code-issues.md).

# Fix Code Issues

On **Projects**, you can remediate scan results across all code categories by adding issues to the fix cart to create a Pull Request (PR) with a suggested fix. For every issue found on Prisma Cloud console, you can view information like origin of the issue in a file or repository, policy violation, and suggestions to remediate the issue.

1. Access scan results on **Projects**.
   1. Select a code category with an issue.
   2. Select an issue from the resource block to view more information and suggested fixes in the resource explorer.
2. Create a PR from the fix recommendation.
   1. Select an issue to see the fix recommendation in the resource explorer.

      You can fix one more issues at once by selecting issues across multiple resources or policy blocks and adding it to the fix cart.
   2. Select **FIX** to add an issue to the fix cart.

      <figure><img src="/files/SMfLvftbzb9Jkb9txwNT" alt="fix pr project fix1.1"><figcaption></figcaption></figure>
   3. Select **Submit** in the 'Resource Explorer' to create a PR with an issue fix.

      <figure><img src="/files/CkApdznu7u8XaNfft5b7" alt="fix pr submit1.1"><figcaption></figcaption></figure>

      The **Naming Method** popup is displayed, offering two options: automated values as provided by by Prisma Cloud, and the option to customize your PR title and branch name.

      <figure><img src="/files/PgEiLde2Obe4nk0PM8m8" alt="fix pr select fix details1.0"><figcaption></figcaption></figure>
3. **Optional**: Customize your Pull Request and Branch names.
   1. Prerequisite: Enable customization by selecting **Application Security** in the left sidebar under 'Configure' > scroll down and enable the **Modify Fix Pull Request (PR) Title and Branch Name** feature.

      **Administrator** privileges are required to enable this setting.

      <figure><img src="/files/7O7WGeRxUtebk8YjAkcO" alt="fix pr enable1.1"><figcaption></figcaption></figure>
   2. Return to step 2.3 above and select **Use custom Pull Request title and branch name**.
   3. Enter a PR title in the Pull Request field
   4. Enter a branch name in the Branch Name field (Optional)
4. Select **Submit**.

   A **Success** message popup confirms that the PR has been successfully opened.

   <figure><img src="/files/pHDqdg6uyS6ufNE0ggOg" alt="fix pr success1.1"><figcaption></figcaption></figure>
5. Click on a link in the popup or access the PR on your VCS console to view the PR.

   If configured, your custom title is displayed in the PR.

   <figure><img src="/files/SeVUq9V8QnPCZJNRCgxH" alt="fix pr repo1.2"><figcaption></figcaption></figure>

For issues with no fix recommendation, you can remediate it by a **Manual Fix** or **Suppress**.

## Fix Vulnerability Issues

On **Projects** **Vulnerabilities** view you see CVE issues that have an automatic fix on the console. You can choose to remediate a single CVE issue or choose to fix all issues in the issue block. When fixing the issue, the CVE **Root version** gets bumped to the latest version from a Pull Request that you need to submit from the **Fix cart**. The issue block will continue to be seen till the Pull Request with the fix is not merged.

1. Select **Application Security > Projects** and then select **Vulnerabilities** view.
2. Access any issue block and then select **Fix** corresponding to the issue.

   Optionally, you can select **Fix All**.

   When fixing the issue, you can verify all CVE’s getting fixed by a verification status corresponding to the CVE.
3. Select **Submit** on the side panel to create a Pull Request (PR) with the fixes.

## Manual Fix an issue

You can perform a manual fix for all issues. A manual fix enables you to access a specific commit to review the code to then resolve the issue manually using the policy guidelines on the Prisma Cloud console.

<figure><img src="/files/Z9bjHmcu9orLjOGDiWvz" alt="proj 24"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/content-collections/application-security/risk-management/monitor-and-manage-code-build/fix-code-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.