Issues
- Use RatingBadge components from Echoes in security reportsSONAR-24756
- Extract `getTaskComponentUrl` from TaskComponent in private codeSONAR-24755
- Normalizes the extension for all templatesSONAR-24753Jeremy
- When enabling the AI codefix settings the fix button shows up after re-loading the pageSONAR-24752
- [FE] Improve aica experienceSONAR-24751
- SonarQube Community Build 25.4SONAR-24750
- Improve SonarGo analysisSONAR-24749Resolved issue: SONAR-24749
- Self-service provisioning of SonarQube Server environmentsSONAR-24748
- Run SonarQube locally without using the zipSONAR-24747
- Remove ElasticSearch from SQSSONAR-24746
- Decouple the workflow framework from issuesSONAR-24745Julien Henry
- Quick and easy installation for non-k8s deploymentsSONAR-24744
- Move Design and Architecture into Early AccessSONAR-24743Resolved issue: SONAR-24743Lucas Paulger
- Write and test proof of concept for replacing CP Subsystem with other Hazelcast classesSONAR-24742
- Research alternative 3rd party librariesSONAR-24741
- Write proof of concept for replacing CP Subsystem with Database table(s)SONAR-24740
- Replace CP Subsystem functionalitySONAR-24739
- Fix flaky test ApplicationNewCodeBBTSONAR-24738Alain Kermis
- BE Hardening 2025.3SONAR-24737
- Utilize time manipulation in telemetry testingSONAR-24736
- Helm: sign release with PGPSONAR-24735
- Use the license to authenticate REST API calls to the SCA domainSONAR-24734
- Configure SQS local feature flags based on the license's featuresSONAR-24733
- Fix ts/lint/test errors and run them in the CISONAR-24732Resolved issue: SONAR-24732Lucas Paulger
- fix height of architecture pageSONAR-24731Resolved issue: SONAR-24731Lucas Paulger
- Stop relying on org.sonar.api.issues.DefaultTransitionsSONAR-24730Resolved issue: SONAR-24730Julien Henry
- Create PR for bumping the versionSONAR-24728
- Run releasibility checkSONAR-24727
- Create the branchSONAR-24726
- Create release ticket (automate this step)SONAR-24725
- [FE] When project is deleted users see both success and error messagesSONAR-24724
- Make JsonDiffParser look for json in LLM responseSONAR-24723
- Fix flaky test on MSSQL upgrade_from_10_8SONAR-24722Resolved issue: SONAR-24722Łukasz Jarocki
- Validate the artifacts publishing mechanismSONAR-24721
- Split the issue workflow definition in twoSONAR-24720Resolved issue: SONAR-24720Julien Henry
- Handle the AI codefix settings page when the API respond with subscription type as nullSONAR-24718
- Link within the AI code fix banner on the admin page is directing users to a blank tabSONAR-24717
- Building SonarQube on Windows takes long timeSONAR-24713
- Computation of portfolios with more than 1000 projects fails on Oracle and MSSQLSONAR-24712Resolved issue: SONAR-24712Duarte Meneses
- Update database requirements to match documentationSONAR-24711
- Cannot update JUnit 5 BOM to 5.12.1SONAR-24709
- Helm: kind test run all instead of one specific chartSONAR-24708
- core-extension-sca: fix test with 10s timeoutSONAR-24706Resolved issue: SONAR-24706Havoc Pennington
- Do not restrict auto-detection for Copilot-generated code to GitHub projectsSONAR-24705
- Remove architecture global stylesSONAR-24704Resolved issue: SONAR-24704Steve Marion
- Disable early access for D&A visualization.SONAR-24703Resolved issue: SONAR-24703Steve Marion
- Upgrade ingress-nginx to 4.12.1SONAR-24702Resolved issue: SONAR-24702Carmine Vassallo
- Include CVEs inside distribution fileSONAR-24701Matteo Mara
- Bump version on maintenance branch.SONAR-24700Resolved issue: SONAR-24700Matteo Mara
- Use RatingBadge components from Echoes in SQS portfoliosSONAR-24699Duarte Meneses
50 of
Use RatingBadge components from Echoes in security reports
General
How
General
How
Description
clones
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
UnassignedUnassignedReporter
David Cho-LeratDavid Cho-LeratEdition
CommunityPriority
Normal
Details
Details
Assignee
Unassigned
UnassignedReporter
David Cho-Lerat
David Cho-LeratEdition
Community
Priority
NormalSentry
Sentry
Sentry
Created 12 hours ago
Updated 12 hours ago
Activity
Show:
CONTEXT
The context can be a subset of an MMF's WHY or any kind of information that helps to understand the higher purpose of the ticket
WHAT
Describe the change using high-level terminology. Ask yourself what kind of information an external user might need to truly grasp what the change is about.
Changes in the Web API (parameters, responses, etc.), or the addition of new endpoints, must be described in the WHAT.