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

Make QT use the same severities for a link as selected in the source #4449

Closed
Sebastiaan127001 opened this issue Aug 25, 2022 · 0 comments · Fixed by #4456
Closed

Make QT use the same severities for a link as selected in the source #4449

Sebastiaan127001 opened this issue Aug 25, 2022 · 0 comments · Fixed by #4456
Assignees
Labels
Feature New, enhanced, or removed feature

Comments

@Sebastiaan127001
Copy link
Contributor

Sebastiaan127001 commented Aug 25, 2022

I'm always frustrated when I click the link to see violations in Sonar and I end up at a page showing all violations.

I would like QT to use a link with the violation severities selected that are used in the source config.

image

image

@Sebastiaan127001 Sebastiaan127001 added the Feature New, enhanced, or removed feature label Aug 25, 2022
@fniessink fniessink self-assigned this Aug 30, 2022
fniessink added a commit that referenced this issue Aug 30, 2022
…issue types (bug, vulnerability, and/or code smell) and severities (info, minor, major, critical, and/or blocker) to the landing URL so that the user sees only the relevant violations when navigating to SonarQube. Closes #4449.
fniessink added a commit that referenced this issue Aug 31, 2022
…issue types (bug, vulnerability, and/or code smell) and severities (info, minor, major, critical, and/or blocker) to the landing URL so that the user sees only the relevant violations when navigating to SonarQube. Closes #4449.
fniessink added a commit that referenced this issue Aug 31, 2022
#4456)

* When measuring violations with SonarQube as source, add the selected issue types (bug, vulnerability, and/or code smell) and severities (info, minor, major, critical, and/or blocker) to the landing URL so that the user sees only the relevant violations when navigating to SonarQube. Closes #4449.
@fniessink fniessink moved this to Released in Quality-time backlog May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New, enhanced, or removed feature
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants