• Support SonarQube™ 10

Other Changes:

• Drop Bitbucket 6 Support

New Features:

• Support SonarQube™ 10

Other Changes:

• Drop Bitbucket 6 Support

Bug fixes:

• Support SonarQube™ with SSO enabled

Bug fixes:

• Support SonarQube™ with SSO enabled

Bug fixes:

• Support SonarQube™ with SSO enabled

Bug fixes:

• Support SonarQube™ with SSO enabled

• Fix XSRF (Cross Site Request Forgery) vulnerability in settings forms
• Fix bug where certain group names could not be saved in the Merge Check override setting

• Fix XSRF (Cross Site Request Forgery) vulnerability in settings forms
• Fix bug where certain group names could not be saved in the Merge Check override setting

• Fix XSRF (Cross Site Request Forgery) vulnerability in settings forms
• Fix bug where certain group names could not be saved in the Merge Check override setting

• Fix XSRF (Cross Site Request Forgery) vulnerability in settings forms
• Fix bug where certain group names could not be saved in the Merge Check override setting

Bug fixes:

• Include the Content-Length header in POST requests to SonarQube™

Bug fixes:

• Include the Content-Length header in POST requests to SonarQube™

Bug fixes:

• Include the Content-Length header in POST requests to SonarQube

Bug fixes:

• Include the Content-Length header in POST requests to SonarQube

Bug fixes:

• Repo config creation race

Bug fixes:

• Repo config creation race

Bug fixes:

• Repo config creation race

Bug fixes:

• Repo config creation race

• Align quality gate status naming to SonarQube™ (PASSED/FAILED)

• Fix links to SonarQube™ in statistics report
• Fix detail link to SonarQube™ in hotspot issue annotation
• Fix disappearing SonarQube™ token in server settings
• Fix icon rendering in Bitbucket 6 on pull request overview
• Fix issue annotation error when author information is not available on a SonarQube™ issue

• Align quality gate status naming to SonarQube™ (PASSED/FAILED)

• Fix links to SonarQube™ in statistics report
• Fix detail link to SonarQube™ in hotspot issue annotation
• Fix disappearing SonarQube™ token in server settings
• Fix icon rendering in Bitbucket 6 on pull request overview
• Fix issue annotation error when author information is not available on a SonarQube™ issue

• Align quality gate status naming to SonarQube™ (PASSED/FAILED)

Bug fixes:

• Fix links to SonarQube™ in statistics report
• Fix detail link to SonarQube™ in hotspot issue annotation
• Fix disappearing SonarQube™ token in server settings
• Fix icon rendering in Bitbucket 6 on pull request overview
• Fix issue annotation error when author information is not available on a SonarQube™ issue

• Align quality gate status naming to SonarQube™ (PASSED/FAILED)

• Fix links to SonarQube™ in statistics report
• Fix detail link to SonarQube™ in hotspot issue annotation
• Fix disappearing SonarQube™ token in server settings
• Fix icon rendering in Bitbucket 6 on pull request overview
• Fix issue annotation error when author information is not available on a SonarQube™ issue

Improvements:

* Consider only changed SonarQube™ projects in a pull request for merge checks and statistics overview

Bug fixes:

* Prevent invalid SonarQube™ Display URL input

* Fix error that prevents user token creation in Bitbucket 8

Improvements:

* Consider only changed SonarQube™ projects in a pull request for merge checks and statistics overview

Bug fixes:

* Prevent invalid SonarQube™ Display URL input

* Fix error that prevents user token creation in Bitbucket 8

Improvements:

* Consider only changed SonarQube™ projects in a pull request for merge checks and statistics overview

Bug fixes:

* Prevent invalid SonarQube™ Display URL input

* Fix error that prevents user token creation in Bitbucket 8

Improvements:

* Consider only changed SonarQube™ projects in a pull request for merge checks and statistics overview

Bug fixes:

* Prevent invalid SonarQube™ Display URL input

* Fix error that prevents user token creation in Bitbucket 8

* Bitbucket 8 compatible release

* Bitbucket 8 compatible release

Bug fixes:

* Prevent NullPointerException in Sonar repository configuration

Bug fixes:

* Prevent NullPointerException in Sonar repository configuration

New Features:

* Support multiple SonarQube projects in a single repository

Bug fixes:

* Provisioning does not copy settings, quality gates etc

* Log spam: WARN [SONAR-10] o.a.h.c.p.ResponseProcessCookies Invalid cookie header:

* Pull request statistics cannot be viewed with new code setting"Reference Branch"

* Log Spam: Excessive ERROR logs if a user has no personal access token configured

* Initializing issue assignee field in pull request does not work

* Changing issue severity and type in pull request fails in Bitbucket 7

New Features:

* Support multiple SonarQube projects in a single repository

Bug fixes:

* Provisioning does not copy settings, quality gates etc

* Log spam: WARN [SONAR-10] o.a.h.c.p.ResponseProcessCookies Invalid cookie header:

* Pull request statistics cannot be viewed with new code setting"Reference Branch"

* Log Spam: Excessive ERROR logs if a user has no personal access token configured

* Initializing issue assignee field in pull request does not work

* Changing issue severity and type in pull request fails in Bitbucket 7

New features:

* Show security hotspots to review potential vulnerabilities in statistics

* Show programming languages for line of code metric in statistics

Bug fixes:

* Cached Sonar PR lookup can prevent code insight annotations if webhook arrival <60 s after last cache load

* Code insight report does not link to the pull request when pull request analysis was used

Improvements:

* Removed special handling for SQ 6.7 for fetching issues of not-analyzed components

New features:

* Show security hotspots to review potential vulnerabilities in statistics

* Show programming languages for line of code metric in statistics

Bug fixes:

* Cached Sonar PR lookup can prevent code insight annotations if webhook arrival <60 s after last cache load

* Code insight report does not link to the pull request when pull request analysis was used

Improvements:

* Removed special handling for SQ 6.7 for fetching issues of not-analyzed components

Bug fixes:

* Fix illegal branch character replacement handling for older SonarQube versions

Bug fixes:

* Fix illegal branch character replacement handling for older SonarQube versions

Bug fixes:

* Fix links to SonarCloud.io dashboard

Bug fixes:

* Fix links to SonarCloud.io dashboard

Bug fixes:

* Fix error logs on ref change events in repositories where Sonar for Bitbucket is disabled

* Fix missing quality gate status link on the pull request detail view for Bitbucket 6.x

Bug fixes:

* Fix error logs on ref change events in repositories where Sonar for Bitbucket is disabled

* Fix missing quality gate status link on the pull request detail view for Bitbucket 6.x

Improvements:

* Simplified SonarQube server configuration by auto-detecting the SonarQube edition

* Improved app’s repository settings and removed obsolete options

* Prevent merging in case a SonarQube analysis task is ongoing

* Improved debug logging for a better support experience

* Improved security by deprecating username/password authentication

* Improved display of Sonar annotations to require less space in the PR diff

* Removed compatibility mode for analysis

Bug fixes:

* Removed entering password/user token in the edit server dialog for every change

* Fix "No enabled repository found" in fork based use cases

* Merge checks fail for repos without enabled app configuration

* Only show "Refresh Sonar analysis" button in case the app is enabled for the current repository

* Provide “Refresh Sonar Analysis” button in Bitbucket 6 as well

* Coverage and duplicated lines statistics are not correctly rounded in pull request popup

Improvements:

* Simplified SonarQube server configuration by auto-detecting the SonarQube edition

* Improved app’s repository settings and removed obsolete options

* Prevent merging in case a SonarQube analysis task is ongoing

* Improved debug logging for a better support experience

* Improved security by deprecating username/password authentication

* Improved display of Sonar annotations to require less space in the PR diff

* Removed compatibility mode for analysis

Bug fixes:

* Removed entering password/user token in the edit server dialog for every change

* Fix "No enabled repository found" in fork based use cases

* Merge checks fail for repos without enabled app configuration

* Only show "Refresh Sonar analysis" button in case the app is enabled for the current repository

* Provide “Refresh Sonar Analysis” button in Bitbucket 6 as well

* Coverage and duplicated lines statistics are not correctly rounded in pull request popup

* If no SCM information is available in the webhook, pull requests are not annotated

* If no SCM information is available in the webhook, pull requests are not annotated

* Allow removal of Sonar server configurations, even if repos still reference them

Bug fixes:

* Compatibility mode does not work with SonarQube 8.0.0 or newer

* Allow removal of Sonar server configurations, even if repos still reference them

Bug fixes:

* Compatibility mode does not work with SonarQube 8.0.0 or newer

New features:

* Option to prevent access to all sonar projects in repository settings

Bug fixes:

* Align presentation of duplication and coverage measures to SonarQube

Improvements:

* Simplify merge check settings

* Improved error message when multiple repositories use the same sonar project key

New features:

* Option to prevent access to all sonar projects in repository settings

Bug fixes:

* Align presentation of duplication and coverage measures to SonarQube

Improvements:

* Simplify merge check settings

* Improved error message when multiple repositories use the same sonar project key

Bug fixes:

* Fix Bitbucket 7.13 support, missing backbone-brace module

* Fix Bitbucket 7.13 support, missing backbone-brace module

* Sonar Quality Gates Not Showing in UI in Bitbucket 6.10

* Add missing descriptions for new security-related quality gates

* Personal Server Tokens Prevents Deleting Sonar Server Config

* Sonar Quality Gates Not Showing in UI in Bitbucket 6.10

* Add missing descriptions for new security-related quality gates

* Personal Server Tokens Prevents Deleting Sonar Server Config

* An endless "Fetching data from SonarQube..." spinner can be shown in the file source view of Bitbucket

* When there is no SCM reference during Sonar analysis and webhook callback, the app cannot create annotations in Bitbucket

* Global app settings requires Super Admin permissions, Admin permissions only lead to a permission error

* Error occurs when enabling 'User-level authentication' without any token configured

* SonarQube tags cannot be selected in the combo box of the Sonar annotated panel on first render

Task:

* Return non-successful HTTP error codes from the app in case of SonarQube webhook problems

* Security update for 3rd party library dependencies

* Updated app REST documentation

* Show timeout status label if timeouts occur on pull request and branch lists

* An endless "Fetching data from SonarQube..." spinner can be shown in the file source view of Bitbucket

* When there is no SCM reference during Sonar analysis and webhook callback, the app cannot create annotations in Bitbucket

* Global app settings requires Super Admin permissions, Admin permissions only lead to a permission error

* Error occurs when enabling 'User-level authentication' without any token configured

* SonarQube tags cannot be selected in the combo box of the Sonar annotated panel on first render

Task:

* Return non-successful HTTP error codes from the app in case of SonarQube webhook problems

* Security update for 3rd party library dependencies

* Updated app REST documentation

* Show timeout status label if timeouts occur on pull request and branch lists

Improvements:

* Supports SonarQube 7.7 as lower bound version

* Allow creation of manual webhooks and do not enforce SonarQube admin permissions

* Shows in server config state if the minimum SonarQube version is not given

Bug fixes:

* For main branch with branch in Sonar project key, app shows component not found in source file view

* Error "Field 'NO_SONAR_PROJECT_BEHAVIOUR' does not accept null values" when using project settings inheritance

Improvements:

* Supports SonarQube 7.7 as lower bound version

* Allow creation of manual webhooks and do not enforce SonarQube admin permissions

* Shows in server config state if the minimum SonarQube version is not given

Bug fixes:

* For main branch with branch in Sonar project key, app shows component not found in source file view

* Error "Field 'NO_SONAR_PROJECT_BEHAVIOUR' does not accept null values" when using project settings inheritance

Bug fixes:

* Internal server error for /rest/sonar4stash/1.0/sonar-server-configs when upgrading from 2.6.x to 3.x

* Unable to see Sonar statistics on pull requests with commercial SonarQube editions for branches containing "/"

Improvements:

* Improve description and enforce community edition for enabling illegal branch characters option

Bug fixes:

* Internal server error for /rest/sonar4stash/1.0/sonar-server-configs when upgrading from 2.6.x to 3.x

* Unable to see Sonar statistics on pull requests with commercial SonarQube editions for branches containing "/"

Improvements:

* Improve description and enforce community edition for enabling illegal branch characters option

* Global branch name character replacement option

Bug fixes:

* When project analysis got started, but is not finished yet, the app shows an empy quality gate status

* Removed unused dependency to SnakeYAML

* Sonar webhook warning on Bitbucket admin page can cause slow page loading

* The error message when users reference a SonarQube server configuration that should get deleted in their personal access tokens page is misleading

Task:

* Prevent using a regular SonarQube account without admin permissions when saving a server configuration

* Global branch name character replacement option

Bug fixes:

* When project analysis got started, but is not finished yet, the app shows an empy quality gate status

* Removed unused dependency to SnakeYAML

* Sonar webhook warning on Bitbucket admin page can cause slow page loading

* The error message when users reference a SonarQube server configuration that should get deleted in their personal access tokens page is misleading

Task:

* Prevent using a regular SonarQube account without admin permissions when saving a server configuration

* Removal of global settings "thread pool size, timeouts, showing quality gate status"

* Removal of "Show quality gate status in lists" option

* Removal of "Prevent failed or in-progress builds" option

* Removal of custom merge checks and instead use quality gate based merge checks

* Removal of "Show behind warning" option

* Removal of "Show only new issues" option

* Removal of branch-based analysis build type and use leak period everywhere

* Dropped support for SonarQube versions < 7.8

Bug fixes:

* Quality gates cannot be copied for SQ versions >= 8.4 due to its change to alphanumeric IDs

* Do not log error in case a branch got deleted and related repository configuration cannot be found

* CSS padding override causes display issues

* /tags API call neeeds to use organization key, otherwise it times out for SonarCloud

Task:

* Add /rest/sonar4stash/1.0/user-tokens/USER_SLUG endpoint to Swagger documentation

* Removal of global settings "thread pool size, timeouts, showing quality gate status"

* Removal of "Show quality gate status in lists" option

* Removal of "Prevent failed or in-progress builds" option

* Removal of custom merge checks and instead use quality gate based merge checks

* Removal of "Show behind warning" option

* Removal of "Show only new issues" option

* Removal of branch-based analysis build type and use leak period everywhere

* Dropped support for SonarQube versions < 7.8

Bug fixes:

* Quality gates cannot be copied for SQ versions >= 8.4 due to its change to alphanumeric IDs

* Do not log error in case a branch got deleted and related repository configuration cannot be found

* CSS padding override causes display issues

* /tags API call neeeds to use organization key, otherwise it times out for SonarCloud

Task:

* Add /rest/sonar4stash/1.0/user-tokens/USER_SLUG endpoint to Swagger documentation

Bug fixes:

* Fix Bitbucket 7.13 support, missing backbone-brace module

Bug fixes:

* Fix Bitbucket 7.13 support, missing backbone-brace module

* Commas in Sonar pull request branch names lead to a "Statistics not found error"

* Webhook from Sonar results in database exception on Oracle

Task:

* Log Sonar project key in case of permission errors

* Commas in Sonar pull request branch names lead to a "Statistics not found error"

* Webhook from Sonar results in database exception on Oracle

Task:

* Log Sonar project key in case of permission errors

* In pull request from fork to other fork repository, when the origin does not have a Sonar configuration, the error "Either Sonar master project key or project base key must exist in repository settings" can come up

* When project settings inheritance is enabled, then option "Use new Sonar branching and pull request support" is not used correctly when collecting issues

* Branch statistics on the repository source page are not shown if option "Show pull request statistics" was disabled even when "Show branch statistics" was enabled

* Error message is not shown in case the Sonar project doesn't exist on pull request detail page

* Statistics link in pull request detail is shown even if app is disabled for repository

* Security vulnerability in used jackson-databind dependency version 2.4.5

* Security vulnerability in used plexus-utils dependency version 3.0.10

* Error "Repository XYZ must have a configuration" comes up in cross-repository pull reque...

* ...

* In pull request from fork to other fork repository, when the origin does not have a Sonar configuration, the error "Either Sonar master project key or project base key must exist in repository settings" can come up

* When project settings inheritance is enabled, then option "Use new Sonar branching and pull request support" is not used correctly when collecting issues

* Branch statistics on the repository source page are not shown if option "Show pull request statistics" was disabled even when "Show branch statistics" was enabled

* Error message is not shown in case the Sonar project doesn't exist on pull request detail page

* Statistics link in pull request detail is shown even if app is disabled for repository

* Security vulnerability in used jackson-databind dependency version 2.4.5

* Security vulnerability in used plexus-utils dependency version 3.0.10

* Error "Repository XYZ must have a configuration" comes up in cross-repository pull reque...

* ...

* Show status of quality gates in "Sonar Statistics" label in pull request details

Bug fixes:

* Issue file link goes to wrong SonarQube page if using legacy branching

* Duplicate code insight report annotations for Sonar can occur

* Error "requirement failed: Pull request with ID not found" when using compatibility mode and forks

* Annotations cannot be created when using "Require personal SonarQube account for all requests"

* Adding a Sonar user token and deleting it again causes "an error occurred"

* "an error occurred" comes up when when the current user doesn't have a user token configured but this is forced in the SonarQube server configuration

* If "require personal SonarQube account for all requests" is enabled and no token is configured, "an error occurred" comes up

* Show status of quality gates in "Sonar Statistics" label in pull request details

Bug fixes:

* Issue file link goes to wrong SonarQube page if using legacy branching

* Duplicate code insight report annotations for Sonar can occur

* Error "requirement failed: Pull request with ID not found" when using compatibility mode and forks

* Annotations cannot be created when using "Require personal SonarQube account for all requests"

* Adding a Sonar user token and deleting it again causes "an error occurred"

* "an error occurred" comes up when when the current user doesn't have a user token configured but this is forced in the SonarQube server configuration

* If "require personal SonarQube account for all requests" is enabled and no token is configured, "an error occurred" comes up

* IMPORTANT: this release uses SonarQube webhooks to get notified of new analysis results: for SonarQube < 7.8, a webhook must be manually created (please see the app's admin area for more information)

* Bitbucket 7 compatibility

* Restrict shown projects in the project chooser to the one of the organization the user is part of in SonarCloud

Bug fixes:

* Project files are not correctly read when using Windows Server for Bitbucket

* When pull request is from two branches of a fork with special pull request support enabled, error message "requirement failed: Pull request with ID X not found" comes up

* Issue rule link doesn't work on SonarCloud due to missing organization key

* IMPORTANT: this release uses SonarQube webhooks to get notified of new analysis results: for SonarQube < 7.8, a webhook must be manually created (please see the app's admin area for more information)

* Bitbucket 7 compatibility

* Restrict shown projects in the project chooser to the one of the organization the user is part of in SonarCloud

Bug fixes:

* Project files are not correctly read when using Windows Server for Bitbucket

* When pull request is from two branches of a fork with special pull request support enabled, error message "requirement failed: Pull request with ID X not found" comes up

* Issue rule link doesn't work on SonarCloud due to missing organization key

* An endless "Fetching data from SonarQube..." spinner can come up in the file source view

* An endless "Fetching data from SonarQube..." spinner can come up in the file source view

* Sonar Repo config access fails for forks where SonarQube is not enabled in v2.7.3

* Do not log error in case a branch got deleted and related repository configuration cannot be found

* Sonar Repo config access fails for forks where SonarQube is not enabled in v2.7.3

* Do not log error in case a branch got deleted and related repository configuration cannot be found

* Commas in Sonar pull request branch names lead to a "Statistics not found error"

Task:

* Log Sonar project key in case of permission errors

* Commas in Sonar pull request branch names lead to a "Statistics not found error"

Task:

* Log Sonar project key in case of permission errors

* Restrict shown projects in the project chooser to the one of the organization the user is part of in SonarCloud

Bug fixes:

* In pull request from fork to other fork repository, when the origin does not have a Sonar configuration, the error "Either Sonar master project key or project base key must exist in repository settings" can come up

* File link in issue details does not work when using SonarQube >= 7.6 community edition

* Branch statistics on the repository source page are not shown if option "Show pull request statistics" was disabled even when "Show branch statistics" was enabled

* Security vulnerability in used plexus-utils dependency version 3.0.10

* Error "Repository XYZ must have a configuration" comes up in cross-repository pull requests

* When a SonarQube server configuration gets deleted, and a user token still references that server configuration, a DB foreign key violation is shown

* Issue rule link doesn't work on SonarC...

* ...

* Restrict shown projects in the project chooser to the one of the organization the user is part of in SonarCloud

Bug fixes:

* In pull request from fork to other fork repository, when the origin does not have a Sonar configuration, the error "Either Sonar master project key or project base key must exist in repository settings" can come up

* File link in issue details does not work when using SonarQube >= 7.6 community edition

* Branch statistics on the repository source page are not shown if option "Show pull request statistics" was disabled even when "Show branch statistics" was enabled

* Security vulnerability in used plexus-utils dependency version 3.0.10

* Error "Repository XYZ must have a configuration" comes up in cross-repository pull requests

* When a SonarQube server configuration gets deleted, and a user token still references that server configuration, a DB foreign key violation is shown

* Issue rule link doesn't work on SonarC...

* ...

* In leak period mode, when Sonar token is enforced and also configured, "SonarQube user token is required" error comes up

* "Error while fetching Sonar projects" comes up when project is selected in repository settings when "Require personal SonarQube account for all requests" is enabled

* Error "requirement failed: Pull request with ID not found" when using compatibility mode and forks

* Adding a Sonar user token and deleting it again causes "an error occurred"

* "Plug-in config must exist at this time" error in fork with compatibility mode enabled

* In leak period mode, when Sonar token is enforced and also configured, "SonarQube user token is required" error comes up

* "Error while fetching Sonar projects" comes up when project is selected in repository settings when "Require personal SonarQube account for all requests" is enabled

* Error "requirement failed: Pull request with ID not found" when using compatibility mode and forks

* Adding a Sonar user token and deleting it again causes "an error occurred"

* "Plug-in config must exist at this time" error in fork with compatibility mode enabled

* Various performance improvements

Bug fixes:

* Rounding issues for "no decrease in coverage merge" check

* Various performance improvements

Bug fixes:

* Rounding issues for "no decrease in coverage merge" check

* "An error occured while getting data from Sonar: null" can occur in some projects

* "An error occured while getting data from Sonar: null" can occur in some projects

* Duplicated code popup cannot be opened in Bitbuckets source view

* Error "Sonar for Bitbucket failed" can come up in pull requests due to caching problem

Task:

* Improved explanation on how to create a SonarQube user token

* Duplicated code popup cannot be opened in Bitbuckets source view

* Error "Sonar for Bitbucket failed" can come up in pull requests due to caching problem

Task:

* Improved explanation on how to create a SonarQube user token

* "Repository must have a configuration" error when fork doesn't have any Sonar settings

* Do not allow to configure "inherit from project" option in forks with the REST API

* "An unknown error occurred" in repository forks for users not permitted to see origin repository

* "The 'component' parameter is missing" error comes up when using SonarQube 8.1

Task:

* Performance improvements

* "Repository must have a configuration" error when fork doesn't have any Sonar settings

* Do not allow to configure "inherit from project" option in forks with the REST API

* "An unknown error occurred" in repository forks for users not permitted to see origin repository

* "The 'component' parameter is missing" error comes up when using SonarQube 8.1

Task:

* Performance improvements

* When a fork owner has project settings of the app from earlier versions, a "Plug-in config must exist at this time" error comes up in the forks

* When a fork owner has project settings of the app from earlier versions, a "Plug-in config must exist at this time" error comes up in the forks

* Error "Could not find neither branch nor pull request" can come up in pull requests

* A wrong branch can be shown in the QG status of the pull request analysis

* For legacy branch projects with master branch analysis without ":master" in the project key, Sonar data cannot be displayed in the souce view

* When issue has no assignee, empty field is shown instead of "Unassigned"

* App shows Sonar information in repository forks even when Sonar is disabed in the fork settings

* Non-severe log message "failed to determine the branch type for ..." is logged with log level ERROR instead of WARNING

* If a repository has Sonar disabled, the quality gate status of all subsequent pull requests in the dasboard is marked as UNKNOWN

* Show blank column instead of "not available" for the quality gate status of repositories where the app is disabled

* Project name does not change properly in repository settings when similar named projects exist

* App doesn...

* ...

* Error "Could not find neither branch nor pull request" can come up in pull requests

* A wrong branch can be shown in the QG status of the pull request analysis

* For legacy branch projects with master branch analysis without ":master" in the project key, Sonar data cannot be displayed in the souce view

* When issue has no assignee, empty field is shown instead of "Unassigned"

* App shows Sonar information in repository forks even when Sonar is disabed in the fork settings

* Non-severe log message "failed to determine the branch type for ..." is logged with log level ERROR instead of WARNING

* If a repository has Sonar disabled, the quality gate status of all subsequent pull requests in the dasboard is marked as UNKNOWN

* Show blank column instead of "not available" for the quality gate status of repositories where the app is disabled

* Project name does not change properly in repository settings when similar named projects exist

* App doesn...

* ...

* Error "Sonar for Bitbucket failed, An unknown error occurred" can come up in a pull request when a project analysis failed

* App tries to get the QG status in branch and pull request list even when disabled for that repository

* Issues with caching of quality gate status can occur

* Error "Sonar for Bitbucket failed, An unknown error occurred" can come up in a pull request when a project analysis failed

* App tries to get the QG status in branch and pull request list even when disabled for that repository

* Issues with caching of quality gate status can occur

* "Sonar for Bitbucket failed" error can come up when using forks

* "Error while determining if Sonar statistics should be shown" error can come up for some users in a pull request

* "refs/pull-requests//from does not exist" error when using special pull request branches option

* "Sonar for Bitbucket failed" error can come up when using forks

* "Error while determining if Sonar statistics should be shown" error can come up for some users in a pull request

* "refs/pull-requests//from does not exist" error when using special pull request branches option

* New global option to disable showing the quality gate status in branch and pull request list

Bug fixes:

* If a project wasn't analyzed yet, the quality gate status is shown as "null" in the pull request and branch list

* Sonar data is fetched from upstream Sonar project instead of the one from the fork

Task:

* Reduce amount of requests to /qg-status in pull request list, branch list and dashboard

* New global option to disable showing the quality gate status in branch and pull request list

Bug fixes:

* If a project wasn't analyzed yet, the quality gate status is shown as "null" in the pull request and branch list

* Sonar data is fetched from upstream Sonar project instead of the one from the fork

Task:

* Reduce amount of requests to /qg-status in pull request list, branch list and dashboard

* Bitbucket user profile Sonar settings yields page not found error when user slug contains an email address

* Bitbucket user profile Sonar settings yields page not found error when user slug contains an email address

* "target not found" error can occur when using pull request branches with SQ 7.7

* "target not found" error can occur when using pull request branches with SQ 7.7

New features:

* Support for SonarQube 8

Bug fixes:

* Caching issues with outdated merge checks and quality gate status display

* NPE can occur when using forks

* Leak period length is not correctly shown in SonarQube > 7.9

* When multiple projects with legacy branching have the same name prefix, project provisioning can fail

* "Unparsable date" error sometimes comes up in the pull request view

* "You are not permitted to access this resource" error on pull request dashboard when user does not have permissions for origin repository of pull request

* SonarQube pull request branches are not deleted when the Bitbucket pull request is deleted

New features:

* Support for SonarQube 8

Bug fixes:

* Caching issues with outdated merge checks and quality gate status display

* NPE can occur when using forks

* Leak period length is not correctly shown in SonarQube > 7.9

* When multiple projects with legacy branching have the same name prefix, project provisioning can fail

* "Unparsable date" error sometimes comes up in the pull request view

* "You are not permitted to access this resource" error on pull request dashboard when user does not have permissions for origin repository of pull request

* SonarQube pull request branches are not deleted when the Bitbucket pull request is deleted

* "ref not found" error when using forks

* "ref not found" error when using forks

* Issues with long descriptions are not properly displayed in the issue overview dialog

* Under certain conditions an exception occurs when getting the quality gate status

* Caching of merge checks and statistics does not work with new branching plug-in when using short-living branches

* Issues with long descriptions are not properly displayed in the issue overview dialog

* Under certain conditions an exception occurs when getting the quality gate status

* Caching of merge checks and statistics does not work with new branching plug-in when using short-living branches

* App cannot be enabled anymore in Bitbucket 6.6.1

* App cannot be enabled anymore in Bitbucket 6.6.1

* Using new branches and pull requests feature leads to too many calls to /api/project_pull_requests

* Partially covered code branches are shown as covered when using SonarQube 7.9

* File link from pull request issue details panel does not link to correct branch

* When using SonarCloud, the master project is not selected in the repository settings

* Cache quality gate status for better performance

* Using new branches and pull requests feature leads to too many calls to /api/project_pull_requests

* Partially covered code branches are shown as covered when using SonarQube 7.9

* File link from pull request issue details panel does not link to correct branch

* When using SonarCloud, the master project is not selected in the repository settings

* Cache quality gate status for better performance

* Sonar project combobox in repository settings yields "JSONObject[id] not found" error

* Use new branches option is taken from repo settings instead project settings when project inheritance is used

* In branch-based mode, new code coverage instead of overall coverage is used for the merge check "Duplicate code max. increase in %"

* "No decrease in unit test coverage" merge check uses the configured test coverage type and not always unit test coverage

* User token check causes too many DB queries

Task:

* Lower compatibility bound for Bitbucket 5.0

* Renamed test coverage options to reflect usage of common coverage in SQ >= 7.7

* Sonar project combobox in repository settings yields "JSONObject[id] not found" error

* Use new branches option is taken from repo settings instead project settings when project inheritance is used

* In branch-based mode, new code coverage instead of overall coverage is used for the merge check "Duplicate code max. increase in %"

* "No decrease in unit test coverage" merge check uses the configured test coverage type and not always unit test coverage

* User token check causes too many DB queries

Task:

* Lower compatibility bound for Bitbucket 5.0

* Renamed test coverage options to reflect usage of common coverage in SQ >= 7.7

* Improved naming of "Use special pull request branches" option so that it cannot be confused with SQ's new pull request analysis

* Support syncing quality gates in project provisioning

Bug fixes:

* Error during project provisioning "Could not connect Sonar server at POST https://our.hostname.here()"

* When clicking on a green quality gate status icon, the popup never finishes to load

* App cannot find analyzed pull request when it is not available in SonarQube during pull request creation

* When option "Replacement for illegal branch characters" is enabled and compatibility mode is used, an error "object not found" comes up and issue information cannot be shown

* NullPointerException when creating Sonar server configurations via REST with token but no password

* Improved naming of "Use special pull request branches" option so that it cannot be confused with SQ's new pull request analysis

* Support syncing quality gates in project provisioning

Bug fixes:

* Error during project provisioning "Could not connect Sonar server at POST https://our.hostname.here()"

* When clicking on a green quality gate status icon, the popup never finishes to load

* App cannot find analyzed pull request when it is not available in SonarQube during pull request creation

* When option "Replacement for illegal branch characters" is enabled and compatibility mode is used, an error "object not found" comes up and issue information cannot be shown

* NullPointerException when creating Sonar server configurations via REST with token but no password

* "The 'component' parameter is missing" error comes up when using SonarQube 8.1

* 'JSONObject["id"] not found' error when using SonarQube 8.1

* Project name does not change properly in repository settings when similar named projects exist

* "The 'component' parameter is missing" error comes up when using SonarQube 8.1

* 'JSONObject["id"] not found' error when using SonarQube 8.1

* Project name does not change properly in repository settings when similar named projects exist

* App's own coverage merge check does not use new code coverage in branch-based mode

* "Sonar for Bitbucket Failed" error in SonarQube 6.7 when using branch plug-in

* Changes to issue type field "Max. number of new Sonar issues with min. severity" are not displayed correctly when using REST API

* "null" error message with some pull request diffs

* App's own coverage merge check does not use new code coverage in branch-based mode

* "Sonar for Bitbucket Failed" error in SonarQube 6.7 when using branch plug-in

* Changes to issue type field "Max. number of new Sonar issues with min. severity" are not displayed correctly when using REST API

* "null" error message with some pull request diffs

* App's own coverage merge check does not use new code coverage in branch-based mode

* "Sonar for Bitbucket Failed" error in SonarQube 6.7 when using branch plug-in

* Changes to issue type field "Max. number of new Sonar issues with min. severity" are not displayed correctly when using REST API

* "null" error message with some pull request diffs

* App's own coverage merge check does not use new code coverage in branch-based mode

* "Sonar for Bitbucket Failed" error in SonarQube 6.7 when using branch plug-in

* Changes to issue type field "Max. number of new Sonar issues with min. severity" are not displayed correctly when using REST API

* "null" error message with some pull request diffs

* View and add Sonar issue comments in Bitbucket

* Support duplicated code and size metrics for short-living branches when using SQ 7.7

* Support pull request analysis with sonar.pullrequest.key

Bug fixes:

* Avoid unnecessary error log entries

* No coverage decrease merge check fails to reject pull requests in certain situations

* Cached merge check results are not invalidated when error occurred

* If auto toggle statistics is enabled, coverage/duplication pie charts are not shown

* Slow event listener in SonarBuildFilesCacheCleaner

* LessCompilationException in server log when going to Sonar admin and user token page

* Merge is allowed when no quality gate info available

* NoSuchElementException in pull request diff

* Line coverage markers are not shown with SQ 7.7

* Sonar statistics not found when using SonarCloud

* Provisioning of structured multi-value properties doesn't work

* Issue severity icons, user selector and cach...

* ...

* View and add Sonar issue comments in Bitbucket

* Support duplicated code and size metrics for short-living branches when using SQ 7.7

* Support pull request analysis with sonar.pullrequest.key

Bug fixes:

* Avoid unnecessary error log entries

* No coverage decrease merge check fails to reject pull requests in certain situations

* Cached merge check results are not invalidated when error occurred

* If auto toggle statistics is enabled, coverage/duplication pie charts are not shown

* Slow event listener in SonarBuildFilesCacheCleaner

* LessCompilationException in server log when going to Sonar admin and user token page

* Merge is allowed when no quality gate info available

* NoSuchElementException in pull request diff

* Line coverage markers are not shown with SQ 7.7

* Sonar statistics not found when using SonarCloud

* Provisioning of structured multi-value properties doesn't work

* Issue severity icons, user selector and cach...

* ...

New features:

* Support for Bitbucket 6

New features:

* Support for Bitbucket 6

New features:

* Support for SonarQube 7.6

Bug fixes:

* For showing pull request quality gate status in the dashboard, an unnecessary amount of requests are executed to check if the feature is enabled

New features:

* Support for SonarQube 7.6

Bug fixes:

* For showing pull request quality gate status in the dashboard, an unnecessary amount of requests are executed to check if the feature is enabled

New features:

* Show duplication in short-living branches in SQ 7.5

* Show a warning if the project key in Maven or SonarRunner projects does not match the chosen one in the repository settings

Bug fixes:

* No coverage decrease merge check threshold is not based on rounded numbers

* Sonar error when showing non-analyzed files in pull requests

* Internal server error in admin screen when using MySQL 5.1

* The branch plug-in existence check doesn't work with all Sonar versions

* In certain situations the warning for in-progress and failed builds is not shown in the Bitbucket source view

New features:

* Show duplication in short-living branches in SQ 7.5

* Show a warning if the project key in Maven or SonarRunner projects does not match the chosen one in the repository settings

Bug fixes:

* No coverage decrease merge check threshold is not based on rounded numbers

* Sonar error when showing non-analyzed files in pull requests

* Internal server error in admin screen when using MySQL 5.1

* The branch plug-in existence check doesn't work with all Sonar versions

* In certain situations the warning for in-progress and failed builds is not shown in the Bitbucket source view

* Show app version in repository and project settings

* Support for test coverage in short-living branches when using SQ >= 7.4

* Create audit log entries when app is enabled/disabled for a repository

* Show a warning if there are any in-progress or failed builds in the Bitbucket source view

Bug fixes:

* File-level issues are not shown on context lines if complete file is shown in the diff

* NPE in certain scenarios where the app cannot determine the base directory of a Maven module

* Do not log NoSuchObjectException for deleted branches

* Show app version in repository and project settings

* Support for test coverage in short-living branches when using SQ >= 7.4

* Create audit log entries when app is enabled/disabled for a repository

* Show a warning if there are any in-progress or failed builds in the Bitbucket source view

Bug fixes:

* File-level issues are not shown on context lines if complete file is shown in the diff

* NPE in certain scenarios where the app cannot determine the base directory of a Maven module

* Do not log NoSuchObjectException for deleted branches

Bug fixes:

• Umlauts in issue assignees are not properly encoded
• Sonar project properties like coverage exclusions which can have multiple patterns are not properly copied for SonarQube > 6.3
• When Sonar user tokens are used, the project cleanup function doesn't delete the Sonar project
• When pull request branches feature is used "Problem retrieving a value from cache" error is thrown in Bitbucket source view
• Project key is required even if app is disabled for a repository
• When using pull request branches option with project settings override, the value from the repository settings is taken instead

Bug fixes:

• Umlauts in issue assignees are not properly encoded
• Sonar project properties like coverage exclusions which can have multiple patterns are not properly copied for SonarQube > 6.3
• When Sonar user tokens are used, the project cleanup function doesn't delete the Sonar project
• When pull request branches feature is used "Problem retrieving a value from cache" error is thrown in Bitbucket source view
• Project key is required even if app is disabled for a repository
• When using pull request branches option with project settings override, the value from the repository settings is taken instead

Bug fixes:

• Umlauts in issue assignees are not properly encoded
• Sonar project properties like coverage exclusions which can have multiple patterns are not properly copied for SonarQube > 6.3
• When Sonar user tokens are used, the project cleanup function doesn't delete the Sonar project
• When pull request branches feature is used "Problem retrieving a value from cache" error is thrown in Bitbucket source view
• Project key is required even if app is disabled for a repository
• When using pull request branches option with project settings override, the value from the repository settings is taken instead

Bug fixes:

• Umlauts in issue assignees are not properly encoded
• Sonar project properties like coverage exclusions which can have multiple patterns are not properly copied for SonarQube > 6.3
• When Sonar user tokens are used, the project cleanup function doesn't delete the Sonar project
• When pull request branches feature is used "Problem retrieving a value from cache" error is thrown in Bitbucket source view
• Project key is required even if app is disabled for a repository
• When using pull request branches option with project settings override, the value from the repository settings is taken instead

Bug fixes:

• SonarQube links in statistics are not working in source view when branch feature is enabled
• Do not fail merge checks if triggered by a technical user
• The app doesn't refresh the merge check cache when a refresh is enforced in the pull request statistics

Bug fixes:

• SonarQube links in statistics are not working in source view when branch feature is enabled
• Do not fail merge checks if triggered by a technical user
• The app doesn't refresh the merge check cache when a refresh is enforced in the pull request statistics

Bug fixes:

• SonarQube links in statistics are not working in source view when branch feature is enabled
• Do not fail merge checks if triggered by a technical user
• The app doesn't refresh the merge check cache when a refresh is enforced in the pull request statistics

Bug fixes:

• SonarQube links in statistics are not working in source view when branch feature is enabled
• Do not fail merge checks if triggered by a technical user
• The app doesn't refresh the merge check cache when a refresh is enforced in the pull request statistics

* Show exact location of issue in side-by-side editor by underlying

* Show Sonar statistics on repository source page

Bug fixes:

* History in source view is not supported with app

* Changing tags in issues can have no effect in certain scenarios

* In MSBuild projects with multiple files having the same name, the plug-in cannot correctly differentiate them

* Quality gate status column is too wide in pull request lists

* Show exact location of issue in side-by-side editor by underlying

* Show Sonar statistics on repository source page

Bug fixes:

* History in source view is not supported with app

* Changing tags in issues can have no effect in certain scenarios

* In MSBuild projects with multiple files having the same name, the plug-in cannot correctly differentiate them

* Quality gate status column is too wide in pull request lists

* Plug-in redirects to login screen in public repositories when looking at a file

New features:

* New option to fallback to incremental mode if the target branch doesn't exist

* Allow updating tags in issue panel

* New filter for showing only issues assigned to the current user

* Show issue rule ID in issue panel

* Allow to edit issue type in issue panel

* Allow to edit issue severity in issue panel

* New option to configure Bitbucket user groups for ignoring merge checks

* Cached merged checks based on last project analysis

* Show Sonar issues also in Bitbucket file source view

* Improved "insufficient permissions" error message for issue transitions

* Improved visualization of statistics panel

* Allow to edit issue assignee in issue panel

* Option to configure user token to access SonarQube under the users credentials instead of the global one

* Show quality gate status of branches in pull request and branch list

* Show severity icons in repository settings beside name of severity in dropdown

Bug fixes:

* Quality pr...

* ...

* New option to fallback to incremental mode if the target branch doesn't exist

* Allow updating tags in issue panel

* New filter for showing only issues assigned to the current user

* Show issue rule ID in issue panel

* Allow to edit issue type in issue panel

* Allow to edit issue severity in issue panel

* New option to configure Bitbucket user groups for ignoring merge checks

* Cached merged checks based on last project analysis

* Show Sonar issues also in Bitbucket file source view

* Improved "insufficient permissions" error message for issue transitions

* Improved visualization of statistics panel

* Allow to edit issue assignee in issue panel

* Option to configure user token to access SonarQube under the users credentials instead of the global one

* Show quality gate status of branches in pull request and branch list

* Show severity icons in repository settings beside name of severity in dropdown

Bug fixes:

* Quality pr...

* ...

Bug fixes:

* Fixed UI problem in Sonar issue overview dialog with Bitbucket Server 5.10

Task:

* Mention in the project not found error that a SonarQube server upgrade requires a plug-in restart

* Fixed UI problem in Sonar issue overview dialog with Bitbucket Server 5.10

Task:

* Mention in the project not found error that a SonarQube server upgrade requires a plug-in restart

New features:

* Show warning about possible inaccurate statistics in case last build was failed

* Improved caching of pull request statistics

* Show which repositories use a global Sonar server configuration in the warning message

* Parellize analysis of multi-module Maven and SonarRunner projects

* When a pom.xml or a sonar-project.properties file is part of the pull request diff, an automatic cache invalidation should be done

Bug fixes:

* "Error while fetching projects" when choosing a master project in the repo settings for SonarQube < 6.5

* Show warning about possible inaccurate statistics in case last build was failed

* Improved caching of pull request statistics

* Show which repositories use a global Sonar server configuration in the warning message

* Parellize analysis of multi-module Maven and SonarRunner projects

* When a pom.xml or a sonar-project.properties file is part of the pull request diff, an automatic cache invalidation should be done

Bug fixes:

* "Error while fetching projects" when choosing a master project in the repo settings for SonarQube < 6.5

* Leak period mode should show delta for all statistic values

Bug fixes:

* Plug-in shows errors in merged pull requests even if this is turned off in the plug-in settings

* Warning about non-admin credentials when using SonarCloud is misleading

* Projects cannot be found in the repository settings master combobox when using SonarCloud

* Leak period mode should show delta for all statistic values

Bug fixes:

* Plug-in shows errors in merged pull requests even if this is turned off in the plug-in settings

* Warning about non-admin credentials when using SonarCloud is misleading

* Projects cannot be found in the repository settings master combobox when using SonarCloud

* Parallelised Maven and SonarScanner project file analysis

Bug fixes:

* "Future.filter predicate is not satisfied" error when no analyzed files are part of a pull request

* Parallelised Maven and SonarScanner project file analysis

Bug fixes:

* "Future.filter predicate is not satisfied" error when no analyzed files are part of a pull request

* Fixed min. issue severity problem

* Fixed timeouts that can occur with very large number of projects in the repo settings project chooser

* Fixed timeout issues under heavy load

* Fixed min. issue severity problem

* Fixed timeouts that can occur with very large number of projects in the repo settings project chooser

* Fixed timeout issues under heavy load

* Issue filters for the issue overview dialog

* Show manually resolved issues (currently in gray) in the issue overview dialog as well

* More space for issue descriptions in issue overview dialog

* Link branch to Sonar project in quality gate status

Bug fixes:

* A NullPointerException can happen in merge check when user is not existing

* For non-Maven and non-SonarRunner projects, new files committed after pull request creation are not recognized

* Tags should be ignored for Sonar project provisioning

* Issue filters for the issue overview dialog

* Show manually resolved issues (currently in gray) in the issue overview dialog as well

* More space for issue descriptions in issue overview dialog

* Link branch to Sonar project in quality gate status

Bug fixes:

* A NullPointerException can happen in merge check when user is not existing

* For non-Maven and non-SonarRunner projects, new files committed after pull request creation are not recognized

* Tags should be ignored for Sonar project provisioning

* Project not found error for master branch projects without ":master" key suffix

* An error occurs when the branch plug-in is used and none of the files in the pull request were analyzed by SonarQube 6.7.x

* When using option "use special pull request branch", no issues are found

* Project not found error for master branch projects without ":master" key suffix

* An error occurs when the branch plug-in is used and none of the files in the pull request were analyzed by SonarQube 6.7.x

* When using option "use special pull request branch", no issues are found

New features:

* Performance improvements for branch-based mode

* Linked instructions on how to migrate from old-branching model to new Sonar 6.7 branch plug-in

Bug fixes:

* Custom max. new issues merge check is not triggered

* IndexOutOfBoundsException in the statistics panel when using a flat Sonar project key

* Performance improvements for branch-based mode

* Linked instructions on how to migrate from old-branching model to new Sonar 6.7 branch plug-in

Bug fixes:

* Custom max. new issues merge check is not triggered

* IndexOutOfBoundsException in the statistics panel when using a flat Sonar project key

* When changing to use the new branching feature the Sonar component key cache is not invalidated

* Error in statistics for SonarQube 6.3-6.5: "Either 'componentId' or 'componentKey' must be provided, not both"

* When changing to use the new branching feature the Sonar component key cache is not invalidated

* Error in statistics for SonarQube 6.3-6.5: "Either 'componentId' or 'componentKey' must be provided, not both"

New features:

* Improved REST API documentation

* Support for new branch feature of Sonar version 6.7

Bug fixes:

* Changing the Sonar server in the repository settings does not clear the plug-in cache

Task:

* Fix descriptions of reliability, maintenance and security ratings in quality gates

* Link to new getting started guide

* Improve user-facing error when no Sonar data for a file could not be found

* Improved REST API documentation

* Support for new branch feature of Sonar version 6.7

Bug fixes:

* Changing the Sonar server in the repository settings does not clear the plug-in cache

Task:

* Fix descriptions of reliability, maintenance and security ratings in quality gates

* Link to new getting started guide

* Improve user-facing error when no Sonar data for a file could not be found

New features:

* Option to disable issue overview dialog

* Allow to un-resolve fixed issues in issue details window

* Show tags in issue details

* Option to specify if the merge check regex should be applied to the source or target branch

* Show issues that have been resolved since the creation of the pull request to allow reviewing them

* When line 0 is not shown in the unified diff of the pull request, show issues in the file header

Bug fixes:

* When project settings inheritance is used but project settings have not been saved yet, no supportive error message is shown

* Quality gates are not shown when statistics is disabled in plug-in settings

* SonarRunner projects do not work if the sonar-project.properties is in a different root directory than the sources

* When pull request is empty (no files) a timeout occurs

Task:

* Improved performance of merge checks

* Option to disable issue overview dialog

* Allow to un-resolve fixed issues in issue details window

* Show tags in issue details

* Option to specify if the merge check regex should be applied to the source or target branch

* Show issues that have been resolved since the creation of the pull request to allow reviewing them

* When line 0 is not shown in the unified diff of the pull request, show issues in the file header

Bug fixes:

* When project settings inheritance is used but project settings have not been saved yet, no supportive error message is shown

* Quality gates are not shown when statistics is disabled in plug-in settings

* SonarRunner projects do not work if the sonar-project.properties is in a different root directory than the sources

* When pull request is empty (no files) a timeout occurs

Task:

* Improved performance of merge checks