Code Review Assistant for Bitbucket
Code Review Assistant for Bitbucket
Breadcrumbs

Changelog

Version 7.x

7.3.0:

⚠️ Announcements

  • Bitbucket 10 Support

    • Bitbucket 10 was released on September, 8, 2025. With this release, we made our app compatible with the recent changes.

New Features

  • Added Configurable timeout for AIRA requests

    • Up to now, requests to the AI Review Assistant had a timeout of 2 minutes. Passed that delay, AIRA would give up on waiting and return an error.

      The AIRA configuration now allows to tailor this timeout to your usage needs. Go to the repository CRA settings page and change the value in the configuration form.

Bug Fixes

  • Fix handling of similar prompt slugs

    • We fixed a bug where the wrong prompts would used in the following case. If a prompt had a slug beginning by the slug of another template, only the prompt with the smaller slug was considered.

7.2.3:

Improvements

  • Improve LLM responses by not send the noisy /aira <template-name> in the chat messages. Even though that text is meaning less, LLM’s can sometimes give too much importance to the text, which in turn demeans the quality of the responses.

7.2.1:

Bug Fixes

  • Fixed issue where the configured prompt template could not be found when using the /aira command

7.2.0:

⚠️ Announcements

  • Bitbucket 8.9 Required

    • Not all features of the worked on Bitbucket 7.21. Because Atlassian is not supporting Bitbucket 7 anymore, we decided to increase the required version to the oldest Atlassian supports, which is Bitbucket 8.9.

  • Deprecated Legacy Analyzers Removed

    • We removed the legacy analyzers that only worked on Bitbucket 7. If you had analyzers configured in a previous release, you still can see the configuration for them in a read only mode.

Bug Fixes

  • Fixed an issue where the CRA AI assistant run on the Bitbucket listener, potentially slowing down Bitbucket.

7.1.1:

Bug Fixes

  • fixed issue: different repositories can now define custom prompt templates with the same name.

  • fixed issue: clean-up custom prompt templates when a repo is deleted.

  • fixed issue: better handling of 404 errors with Ollama-based AI provider.

7.1.0:

New Features

  • AI Review Assistant works for all API based AI Providers

  • Chat with AI from Pull Requests is now easier

    • It is now easier for Pull Request participants to chat with AIRA. We added a dedicated button to ask a question directly.  And AIRA will immediately let you know it is taking care of your request by reacting with a 👀 emoji.

  • Create Custom Prompts for AI Review Assistant

    • AIRA can be used to

      • “chat” with an AI in the context of a Pull Request

      • ask to generate a title for a new Pull Request

      • ask to generate a description for a new Pull Request

    • You can now create custom prompts to be used for each of these three use cases. With our provided variables, you can choose to insert relevant information from the pull request you want to share with your AI (title, description, diff, commit messages…) and ask for specific structure in the response.

    • Define these custom prompts from the Code Review Assistant settings page in your repository.

    • When you choose to create a new prompt template or edit an existing one, you can adjust the intended usage, name, and templated text:

    • You can also simulate any of the existing prompt templates and see information such as how template variables like <diff> will be replaced with real information from the PR.

7.0.1:

Bug Fixes

  • Bugfix where the app sometimes did not start

  • Bugfix where the logging was not properly initialized

7.0.0:

⚠️ Announcements

  • Bitbucket 9 on Java 17 Support

Version 6.x

6.1.0:

New Features

  • Added features to the AI Review Assistant

    • Suggest Pull Request Description (Bitbucket 8+)

      • When creating pull request, you now can ask the AI assistant to suggest a pull request title and description.

    • /aira Command for Existing Threads

      • Use the /aira command in an existing comment thread to invoke the AI Review Assistant.

    • Support for Azure Open AI

      • We now also support using Azure Open AI or any Open AI API compatible AI provider

  • We now support analyzing build logs with Flake8 and Pylint output.

6.0.0:

New Features

  • AI Review Assistant (Opt-In) 🤖

    • The AI Review Assistant lets you interact with ChatGPT through comments on your pull requests in Bitbucket.

    • Write a comment starting with /aira (short for AI Review Assistant) to talk to ChatGPT.

    • Look at our documentation AI Review Assistant for further information.

Maintenance

  • Added telemetry for improving application usage and performance

    • In a desire of continuously improving the application, Code Review Assistant now gathers data about usage and performance. You can opt out of sending telemetry statistics by setting the Bitbucket property plugin.ch.mibex.stash.cra.telemetry to false.

Bug Fixes

  • Fix missing analysis report caused by disabled Bamboo build job

Version 5.x

5.8.1:

Bug Fixes

  • Fix issue where Bamboo logs are not downloaded, failing with authorization error.

5.8.0:

Improvements

  • Code Insight merge checks - Stable Report keys

    • To use the Code Insight reports generated by Code Review Assistant in the

    • Code Insight merge checks, we changed how the report keys are generated.
      Now they are stable and do not contain any build number or so.

    • Check the official guide from Atlassian, on how to setup Code Insight merge checks to get started.

5.7.0:

Maintenance

  • Migration from OAuth to HTTP access tokens

    • We’ve discovered the OAuth mechanism, which is handled by Bitbucket itself, doesn’t work as we expected. It can’t be configured to use another Bitbucket user, unless you login as that user.

    • Therefore, we switched to use plain HTTP access tokens. Existing OAuth links will continue to work, but no new OAuth connections can be configured. We recommend to migrate to HTTP access tokens.

5.6.1:

Bug Fixes

  • Support old build status REST API

Maintenance

  • Fixes XSRF (Cross Site Request Forgery) vulnerability in settings forms

5.6.0:

New Features

  • Code Review Assistant now support analyzing builds on Jenkins. Read the documentation here.

Improvements

  • Migration Support

    • When the old analyzers are not supported, either because you migrated to Bitbucket 8 or use a multi-node setup, then the old configuration is now show in read only mode. So that is possible to see the old configuration to plan a migration.

Bug Fixes

  • Fixed: Pull Request Templates did not work properly on newer Bitbucket 8 releases.

5.5.1:

Maintenance

  • Added a Bitbucket Server release, to be in sync with the Data Center edition.

5.5.0:

⚠️ Announcements

  • Bitbucket 7.8 Required

    • The minimum version of Bitbucket required for the app is 7.8

New Features

  • OWASP Dependency-Check Support for Maven

    • Code Review Assistant now detects build output of the Maven OWASP Dependency-Check Support plugin. If it detects such a report, it will create a pull request task to make you aware of the vulnerable dependencies:

    • By default only the issues triggering a build failure by violating the threshold failBuildOnCVSS in the pom.xml. You configure or disable the dependency check comment in the repository’s Code Review Assistant settings.

Improvements

  • Toggle Button is turned red when disabled

Bug Fixes

  • Fix Crash on Bitbucket 8 when saving settings which where migrated from an earlier Bitbucket release

  • Fix bug where a unreadable error message was generated with text like `Bamboo$BambooAccess$FailedToConnect Master plan key not found for BAMBOOKEY-42` was shown

5.4.0:

⚠️ Announcements

  • The upcoming version of Bitbucket 8 is now supported. When running on Bitbucket 8, the legacy built-in and custom analyzers are not supported anymore. Please migrate to showing Code Analysis in PR when you plan to move to Bitbucket 8.

  • Bamboo 7.1 or Newer Required

    • The Bamboo 6.x series is no longer supported. Bamboo 7.1 or newer is required for showing Code Analysis in Pull Requests.

Improvements

  • Redirect back to the settings page after the OAuth setup with Bamboo

  • Added information link on how to report missing features.

  • Improved the license handling.

Bug Fixes

  • Handle Bamboo build plans with numbers correctly.

Maintenance

  • Update to third party dependencies

5.3.0:

Maintenance

  • Version 5.3 is functionally the same as 5.2, but is Bitbucket Data Center compatible.

5.2.0:

New Features
Improvements

  • Parse the logs of partially completed builds.

  • Support having multiple build plans for the same repository.

Maintenance

  • Updated vulnerable dependencies.

5.1.0:

⚠️ Announcements

  • We deprecated the Pull Request Templates feature. Bitbucket has built-in pull request description support now. For more advanced checklists, check out Checklist Buddy for Bitbucket.

  • We deprecated the Bug Prediction feature due to lack of demand.

New Features
Bug Fixes

  • Don’t show Code Cross Reference configuration errors on Bitbucket 7, as it isn’t supported on Bitbucket 7.

5.0.0:

⚠️ Announcements

  • Road to Data Center Edition

  • The code cross-reference feature is deprecated.

    • It is not supported on Bitbucket 7 and it only works on Bitbucket 6. As Bitbucket 6 reached its end of life, we will remove this feature in an upcoming release.

New Features

Version 4.x

4.3.0:

Improvements

  • Added the ‘Run CRA analysis’ and ‘Remove CRA annotations’ actions to pull requests in Bitbucket 7:

  • The Code Review Assistant config panel is now accessible to Bitbucket admins and not only system admins.

Bug Fixes

  • In Bitbucket 7, the built in analyzer configuration couldn’t be selected once it was switched to an another file.

  • The JSHint analyzer crashed when the configuration had comments in it, as it expected JSON files.

4.2.0:

⚠️ Announcements

  • Bitbucket Data Center

    • We intend to launch a Data Center approved version of this app. Data Center customers will be required to purchase a Data Center app license upon their next renewal.

Maintenance

  • Updated PMD to 6.39.0 version.

  • Update ScalaStyle to 1.5.1

  • Updated CodeNarc to 2.2.0

  • Confirmed that Code Review Assistant does not use log4j and is not affected by CVE-2021-44228 aka Log4Shell.

4.1.0:

Maintenance

  • Internal changes to allow compatibility with Bitbucket 7.3.

4.0.1:

Bug Fixes

  • Upgraded built-in CodeNarc to version 1.6.1

  • Issues for new commits are not always added deterministically to the pull request

  • Merge checks are not applied for custom static analyzers in Bitbucket >= 7.2

  • Got rid of enforcing %f and %fs for files because it does not work with some analyzers like PMD when single command invocation with all files is required

  • Settings like regexes from locally defined custom analyzers are not applied

4.0.0:

⚠️ Announcements

  • Removal of code cross-referencing feature based on ctags for Bitbucket >= 7.0

    • Due to Bitbucket API changes in version 7, we cannot provide the ctags feature anymore. This is why code cross-referencing is not added to pull requests anymore in newer Bitbucket versions.

New Features

  • Support multi-line static code analysis output

    • Some static code analyzers like pydocstyle emit multi-line output for found code violations. To support that, we now consider multiple lines when applying the configured regular expressions to scan the analyzer output.

  • Bitbucket 7 compatibility

    • Some internal changes to allow compatibility with Bitbucket 7.

Improvements

  • Ignore LFS files when cloning a repository

    • When cloning a repository to execute static code analyzers, we now ignore Git LFS files to reduce the used disk space, but also because these are often binaries that should not get analyzed anyway.

  • Annotations with built-in CodeNarc are not shown due to relative-paths in issue output

  • Upgrade to CodeNarc 1.4

  • Increased timeout for running external analyzers