Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to new SonarQube issue structure #8354

Open
4 tasks
fniessink opened this issue Mar 27, 2024 · 0 comments
Open
4 tasks

Migrate to new SonarQube issue structure #8354

fniessink opened this issue Mar 27, 2024 · 0 comments
Labels
Tech Technical change without significant user impact
Projects

Comments

@fniessink
Copy link
Member

fniessink commented Mar 27, 2024

SonarQube docs:

Tasks:

  • Replace the severity parameter values with low/medium/high and use the impactSeverites parameter for the api/issues/search endpoint
  • Drop the issue type parameter
  • Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
  • Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint

The new issue structure is available in SonarQube >= 10.2. Document this.

@fniessink fniessink added this to Backlog in Backlog via automation Mar 27, 2024
@fniessink fniessink added Source(s) New, enhanced, or removed metric source Tech Technical change without significant user impact and removed Source(s) New, enhanced, or removed metric source labels Mar 27, 2024
@fniessink fniessink moved this from Backlog to Blocked by other issue or time in Backlog Mar 27, 2024
@fniessink fniessink changed the title Migrate to new SonarQube (>=10.4) issue structure and API #7539 Migrate to new SonarQube (>=10.4) issue structure Mar 27, 2024
@fniessink fniessink changed the title Migrate to new SonarQube (>=10.4) issue structure Migrate to new SonarQube issue structure Mar 27, 2024
@fniessink fniessink moved this from Blocked by other issue or time to Refinement agenda in Backlog Mar 27, 2024
@fniessink fniessink moved this from Refinement agenda to Ready in Backlog Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tech Technical change without significant user impact
Projects
Backlog
Ready
Development

No branches or pull requests

1 participant