Hi team,
It’d be really useful to have Jira integration with SonarCloud. Currently we are working on adding code smells and vulnerabilities manually - we will eventually automate this, but it’d be great if this comes out of the box.
Keep up the good work
Hi Ben,
we used to have such a feature in the SonarQube world sometime ago, and we dropped it. You can find a detailed blog post that explains why: https://blog.sonarsource.com/stop-planning-fix-the-leak
To sum up: if you apply the “Fix the leak” concept, you should not have to manage tickets (and therefore action plans) in JIRA to fix quality issues.
Hope this makes sense!
Hi
I’d find this to be a really useful feature. Our Definition of Done includes the stipulation that there should be no code smells and 100% coverage. I don’t want to prevent developers from checking in whilst these criteria are not yet met, before an issue is passed to peer review/QA. Also our build breakers are set slightly more leniently than 0 code smells and 100% coverage overall, even though most “normal” code is expected to adhere to this.
If I could see from the issue in Jira any code smells against any of the commits made for this jira issue, then it would really help to determine that this issue meets the DoD. All our commits (BitBucket/Git) are linked to Jira issue via the comments, and they can be seen against the jira issue under the Development section. Since Sonar recognises the commit that caused code smell, it should be possible to link them together.
Julia
Not voting for Jira integration per say but there is a use case where the new issues are on pre-existing code, but they are new because the quality profiles have changed. These changes are either from an Admin or because sonar cloud was updated with newer rules. So the prior leaks were invisible but now you have a large pool of issues that should be addressed. The same goes for projects with legacy code that predates the integration with Sonar.