SonarQube Issue Sandbox Explained | SonarQube Server 2026.1 LTA Demo

Introduction to Issue Sandboxing

SonarQube Server 2026.1 LTA introduces a significant new capability designed to improve the update experience for organizations managing code quality across their projects. The issue sandbox feature addresses a common challenge that teams face when updating to new versions of SonarQube: the sudden emergence of new issues detected by newly added or updated rules. Rather than immediately impacting quality gates, these newly discovered issues are now isolated in a dedicated sandbox environment, allowing development teams to handle them on their own terms.

How the Feature Works

When users first upgrade to SonarQube Server 2026.1 LTA, they are prompted to enable the issue sandboxing capability through the administration section. Once activated, the system begins isolating any issues discovered by new or modified rules that were added during the update. These sandboxed issues appear in a dedicated "Issue Sandbox" section within the overall code view, separate from existing project issues.

Managing Issues at Your Own Pace

The primary benefit of issue sandboxing is that it decouples quality gate status from newly discovered issues. Even though the system identifies code quality concerns based on new rules, the project's quality gate remains unaffected until the development team explicitly decides to promote these issues from sandbox status to open status. This means teams can review, triage, and plan their response to new findings without experiencing unexpected quality gate failures immediately after an update.

Workflow and Decision Making

When examining a sandboxed issue, users can see that the issue carries an "in sandbox status" designation, clearly distinguishing it from regular open issues. Developers and quality engineers can then take time to evaluate each issue, decide whether it represents a genuine concern for their codebase, and determine the appropriate action. This deliberate, measured approach to issue management ensures that quality gate changes happen only when the team is prepared to address them.

Key Takeaways

• Issue sandboxing isolates newly detected issues from new/updated rules during SonarQube updates, preventing unexpected quality gate failures
• Teams can review and triage sandboxed issues at their own pace before deciding to promote them to open status
• The feature requires a one-time enablement through the administration section when first upgrading to version 2026.1 LTA
• Quality gates remain stable during updates, only changing when teams deliberately move issues out of sandbox status
• This capability significantly improves the update experience by giving organizations greater control over when quality gate impacts occur