Backlog fix suggestions
Let the SonarQube Remediation Agent fix issues in your backlog, on a schedule or for the issues you assign to it. This page is for SonarQube Server 2026.5.
The SonarQube Remediation Agent proposes fixes for the issues found by analysis. It works on the issues in your backlog, generates the changes in the background, and opens a pull request in your repository for you to review and approve.
The Remediation Agent is available in the Enterprise and Data Center editions and requires a separate subscription. An Instance Admin enables it before you can use it. See Remediation Agent.
Your project must be bound to a repository on your DevOps platform, because the agent clones the repository and opens a pull request with its changes.
Assigning issues to the agent
When manual backlog remediation is enabled, you can send issues to the agent from your project:
Go to your project's Issues page.
Select the issues you want fixed.
Select Assign to agent.
You can assign up to 20 issues at a time. If you select more, only the first 20 eligible issues are sent. Issues the agent cannot act on are left out of the selection, and Assign to agent stays unavailable until you select at least one eligible issue.
Assign to agent appears only when an Instance Admin has enabled manual backlog remediation.
The agent works through the issues you assigned and opens a pull request with the changes. Track the job on the Remediation Agent page while it runs.
When automated backlog remediation is enabled, the agent also proposes fixes on a schedule, without anyone assigning issues. See Remediation Agent.
Tracking the agent's jobs
To follow what the agent is doing, go to your project and open the Remediation Agent page. It lists each job with:
Status / Duration
The job's current state: Pending, In progress, Completed, or Failed. Completed and failed jobs also show how long the job took. An in-progress job shows Please wait... instead.
Started
When the job started. Recent jobs show Today or Yesterday.
Source
What the job came from. Backlog issues means someone assigned the issues. Scheduled means automated backlog remediation started the run. Pull request remediation means the job was triggered from a failing pull request; see Pull request fix suggestions.
Outcome
A link to the pull request the agent opened, shown as PR #<number>. Pending and in-progress jobs show a dash, as do completed jobs that did not produce a pull request. A failed job shows Failed with a tooltip giving the reason.
The page shows the number of jobs currently listed. Select Show more to load older jobs.
If the project has no jobs yet, the page shows No agent jobs yet. If the list cannot load, the page shows Something went wrong while loading agent jobs. with a Retry action.
Reviewing the agent's pull request
The agent opens a pull request in the bound repository containing its proposed fixes. Review it the way you review any other pull request in your team's workflow, then merge it to apply the fixes.
The fixed issues close on the next analysis of the target branch, which happens when your CI pipeline analyzes it.
Reviewer assignment
The agent automatically assigns a reviewer to the pull request it opens, using each DevOps platform's native reviewer concept: GitHub reviewers, GitLab approvers, or Azure DevOps required reviewers.
To choose a reviewer, the agent looks for someone who recently worked on the changed files. If a file has no history, it falls back to whoever committed recently elsewhere in the repository.
Reviewer assignment does not block the pull request: if the agent cannot confirm an eligible reviewer, it still opens the pull request without one.
On forked repositories, the agent's candidates can include the upstream project's authors, who are not collaborators on your fork. In that case, reviewer assignment can fail and the pull request opens without a reviewer.
On GitLab, reviewer assignment requires GitLab 16.3 or later. See Reviewer assignment support.
Related pages
Last updated
Was this helpful?