Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sonar for bitbucket plugin now defaults to Leak period for Analysis

We recently upgraded sonar for bitbucket plugin to version 4.3.1 and upgraded bitbucket to version 7.6.5.

Before the Bitbucket upgrade, there was a setting on the Sonar plugin in the project settings to specify whether the analysis should be branch based vs. leak period.

I am no longer seeing this option after the upgrade. From the PRs, it seems like it’s using leak period by default. Is there a way to change it back to branch-based analysis?

1 answer

1 accepted

0 votes
Answer accepted


That is correct, we decided to remove the branch-based analysis mode with version 4.0 of the app.

The reason is that it caused confusion by different issue statistics compared to what SonarQube itself using leak period shows.

You can find more details about the changes of version 4.0 in our release notes:

Please let us know if you have further questions.

Best regards,

Michael (app vendor)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events