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.

Sign up for GitHub

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

Jump to bottom

Migrate to new SonarQube issue structure #8354

Closed
4 of 5 tasks
fniessink opened this issue Mar 27, 2024 · 0 comments · Fixed by #8782
Closed
4 of 5 tasks

Migrate to new SonarQube issue structure #8354

fniessink opened this issue Mar 27, 2024 · 0 comments · Fixed by #8782
Assignees
@fniessink
Labels
Source(s) New, enhanced, or removed metric source

Comments

@fniessink
Copy link
Member

fniessink commented Mar 27, 2024 •
edited
Loading

SonarQube docs:

Tasks:

  • Replace the severity parameter values with low/medium/high and use the impactSeverities parameter for the api/issues/search endpoint.
  • Migrate the severities in existing reports.
  • Migrate the issue type parameter to the new "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint. Bugs become issues with reliability impact, vulnerabilities become issues with security impact, and code smells become issues with maintainability impact.
  • Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint.
  • The new issue structure is available in SonarQube >= 10.2. Document this (in the description, or via Allow for specifying supported versions of sources #8786 if that story gets finished first).
@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 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 added Source(s) New, enhanced, or removed metric source and removed Tech Technical change without significant user impact labels May 27, 2024
@fniessink fniessink moved this from Ready to Development in progress (max 4) in Quality-time backlog May 27, 2024
@fniessink fniessink self-assigned this May 27, 2024
fniessink added a commit that referenced this issue May 27, 2024
@fniessink
Migrate to the new SonarQube issue structure.
010ce79 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- The possible parameter values of the severity parameter are now "low", "medium", and "high". Previously allowed values were "critical", "blocker", "major", "minor", and "info".

TODO:
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
@fniessink fniessink mentioned this issue May 27, 2024
Merged
@fniessink fniessink linked a pull request May 27, 2024 that will close this issue
Migrate to the new SonarQube issue structure. #8782
Merged
fniessink added a commit that referenced this issue May 27, 2024
@fniessink
Migrate to the new SonarQube issue structure.
51b6972 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".

TODO:
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 27, 2024
@fniessink
Migrate to the new SonarQube issue structure.
ac43af0 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".

TODO:
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 28, 2024
@fniessink
Migrate to the new SonarQube issue structure.
6fc2290 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.

TODO:
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 28, 2024
@fniessink
Migrate to the new SonarQube issue structure.
d8b5e03 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.

TODO:
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
c29eb5d 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.

TODO:
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
bc59e71 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter

TODO:
- Change the security_types parameter so it does not depend on the issue type.
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
1e02403 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter

TODO:
- Change the security_types parameter so it does not depend on the issue type.
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
26e66a5 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Change the security_types parameter so it does not depend on the issue type.

TODO:
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
c33e5ca 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Change the security_types parameter so it does not depend on the issue type.

TODO:
- 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
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
ace5e69 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint

TODO:
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 29, 2024
@fniessink
Migrate to the new SonarQube issue structure.
fbe33f5 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint

TODO:
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 30, 2024
@fniessink
Migrate to the new SonarQube issue structure.
917464d 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint

TODO:
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 30, 2024
@fniessink
Migrate to the new SonarQube issue structure.
a866156 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint

TODO:
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 30, 2024
@fniessink
Migrate to the new SonarQube issue structure.
f383dbf 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.

TODO:
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 31, 2024
@fniessink
Migrate to the new SonarQube issue structure.
db48c55 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 31, 2024
@fniessink
Migrate to the new SonarQube issue structure.
a2d8672 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 31, 2024
@fniessink
Migrate to the new SonarQube issue structure.
d4d891c 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue May 31, 2024
@fniessink
Migrate to the new SonarQube issue structure.
5e95e83 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
@fniessink fniessink moved this from Development in progress to Reviewing in progress in Quality-time backlog May 31, 2024
fniessink added a commit that referenced this issue Jun 3, 2024
@fniessink
Migrate to the new SonarQube issue structure.
02808cf 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue Jun 3, 2024
@fniessink
Migrate to the new SonarQube issue structure.
515bece 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue Jun 4, 2024
@fniessink
Migrate to the new SonarQube issue structure.
c3093f8 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Remove the "Severities" parameter.
- Add an "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high".
- Migrate the severity parameter values to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Drop the issue type parameter
- Add a "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue Jun 4, 2024
@fniessink
Migrate to the new SonarQube issue structure.
d6a0569 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Replace the "Severities" parameter with the "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high". Old severity parameter values are migrated to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Replace the issue type parameter with the "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint. Old issue type parameter values are migrated to software qualities (bug -> reliability, vulnerability -> security, code smell -> maintainability).
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint.
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue Jun 4, 2024
@fniessink
Migrate to the new SonarQube issue structure.
47506cf 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Replace the "Severities" parameter with the "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high". Old severity parameter values are migrated to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Replace the issue type parameter with the "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint. Old issue type parameter values are migrated to software qualities (bug -> reliability, vulnerability -> security, code smell -> maintainability).
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint.
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
fniessink added a commit that referenced this issue Jun 4, 2024
@fniessink
Migrate to the new SonarQube issue structure.
6feef96 
Migrate to the new SonarQube issue structure introduced in SonarQube 10.2. This means:
- Replace the "Severities" parameter with the "Impact severities" parameter. The possible values of the impact severity parameter are "low", "medium", and "high". Old severity parameter values are migrated to the new values according to the mapping documented by SonarSource: https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/#severity-mapping.
- Replace the issue type parameter with the "software quality" parameter and use the impactSoftwareQualities parameter for the api/issues/search endpoint. Old issue type parameter values are migrated to software qualities (bug -> reliability, vulnerability -> security, code smell -> maintainability).
- Add a "clean code attribute" parameter and use the cleanCodeAttributeCategories parameter for the api/issues/search endpoint.
- Change the security_types parameter so it does not depend on the issue type.
- Document that the lowest supported SonarQube version is 10.2.

Closes #8354.
@github-project-automation github-project-automation bot moved this from Reviewing in progress to Merged in Quality-time backlog Jun 4, 2024
@fniessink fniessink moved this from Merged to Release candidate released in Quality-time backlog Jun 18, 2024
@fniessink fniessink moved this from Release candidate released to Released in Quality-time backlog Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fniessink fniessink

Labels
Source(s) New, enhanced, or removed metric source
Projects
Quality-time backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrate to the new SonarQube issue structure. ICTU/quality-time
1 participant
@fniessink