Minor version update

In this version of the app, we've added the Cycle Time column, which extends the Bitbucket Pull Requests page and allows you to:

• See objectively whether the development process is getting faster or slower.
• Analyze the correlation of specific metrics with Cycle Time.
• Compare the rates within the organization or across the industry.

Team name editing

We've also added the capability to rename an existing team. To rename a team, navigate to the Teams tab, select the team you want to rename, and then change the name in the team card.

In this version of the app, we've added the Cycle Time column, which extends the Bitbucket Pull Requests page and allows you to:

• See objectively whether the development process is getting faster or slower.
• Analyze the correlation of specific metrics with Cycle Time.
• Compare the rates within the organization or across the industry.

Team name editing

We've also added the capability to rename an existing team. To rename a team, navigate to the Teams tab, select the team you want to rename, and then change the name in the team card.

Universal date filter for Graphs

In this version of the app, we've reimagined user experience, interface, and, in particular, the date filtering on the Graphs page to create a universal filtering panel that applies to all Graphs at the same time, allowing you to set the filtering criteria once and analyze the data from different perspectives going from one graph to another. The updated date filter also made it possible to choose a custom period of any length for Graphs where it wasn't available.

Universal date filter for Graphs

In this version of the app, we've reimagined user experience, interface, and, in particular, the date filtering on the Graphs page to create a universal filtering panel that applies to all Graphs at the same time, allowing you to set the filtering criteria once and analyze the data from different perspectives going from one graph to another. The updated date filter also made it possible to choose a custom period of any length for Graphs where it wasn't available.

Improved data grouping in Resolution Time Distribution report

In this version, we've adjusted the data grouping in the Resolution Time Distribution report so that the last 5% of pull requests that take the longest to resolve are included in a single bar far right. It will increase the readability of the report, as well as improve its performance and user experience, making it easier to spot outliers in the data.

Other updates in this release

• Fixed the issue with the inconsistencies in the calculation of resolution time that could have appeared between the data in the graph and the summary table in the Resolution Time Distribution report.
• Fixed the issue with the graphs and reports failing to load correctly due to a repository being offline.

Improved data grouping in Resolution Time Distribution report

In this version, we've adjusted the data grouping in the Resolution Time Distribution report so that the last 5% of pull requests that take the longest to resolve are included in a single bar far right. It will increase the readability of the report, as well as improve its performance and user experience, making it easier to spot outliers in the data.

Other updates in this release

• Fixed the issue with the inconsistencies in the calculation of resolution time that could have appeared between the data in the graph and the summary table in the Resolution Time Distribution report.
• Fixed the issue with the graphs and reports failing to load correctly due to a repository being offline.

Fixed in this release

• Fixed the repository selector failure in the User Contributions if a user had no activities.

• Improved security and stability of the Activity graph and the Teams selectors.

• Fixed the repository selector failure in the User Contributions if a user had no activities.

• Improved security and stability of the Activity graph and the Teams selectors.

• Fixed the issue with the tooltip displayed incorrectly in the Punchcard graph.

• Fixed the issue with the Activity stream not showing up in the User Contributions due to a failure to load the commit branch.

• Improved the UX of the team creation dialog.

• Fixed the issue with the tooltip displayed incorrectly in the Punchcard graph.

• Fixed the issue with the Activity stream not showing up in the User Contributions due to a failure to load the commit branch.

• Improved the UX of the team creation dialog.

Improved Users filter in the Top Committers Report

Beginning with this version, The Top Committers Report's Users filter no longer includes contributor names but only Bitbucket usernames. In combination with the multi-select filter, it helps you find relevant users and create reports more quickly.

Other updates in this release

• To improve the app's overall security, one of the libraries used in the app has been updated.

Improved Users filter in the Top Committers Report

Beginning with this version, The Top Committers Report's Users filter no longer includes contributor names but only Bitbucket usernames. In combination with the multi-select filter, it helps you find relevant users and create reports more quickly.

Other updates in this release

• To improve the app's overall security, one of the libraries used in the app has been updated.

In this version, we've moved the Commits graph to the report category to become Commit Activity Report. We believe that this category suits the concept behind the graph better, and this change will help us unify the app's features further to achieve better user experience.

Compatibility changes

Beginning with this version, the app compatibility changes to support only Bitbucket version 7.0 or higher. We have certain app UI changes planned shortly, and limiting the compatibility with the older Bitbucket versions will allow us to deliver new functionality faster.

In this version, we've moved the Commits graph to the report category to become Commit Activity Report. We believe that this category suits the concept behind the graph better, and this change will help us unify the app's features further to achieve better user experience.

Compatibility changes

Beginning with this version, the app compatibility changes to support only Bitbucket version 7.0 or higher. We have certain app UI changes planned shortly, and limiting the compatibility with the older Bitbucket versions will allow us to deliver new functionality faster.

• Fixed the issue with the app not indexing pushes to a new branch in Bitbucket 8.3+, which used to pause indexing of a repository until the app restart. The issue could have also caused orphaned commits to be included in the app index. This update is strongly recommended to users of Bitbucket 8.3 and higher.
• Fixed the issue with activities being duplicated on the Contributions page in case of quick switch between the Summary and Detailed views.

• Fixed the issue with the app not indexing pushes to a new branch in Bitbucket 8.3+, which used to pause indexing of a repository until the app restart. The issue could have also caused orphaned commits to be included in the app index. This update is strongly recommended to users of Bitbucket 8.3 and higher.
• Fixed the issue with activities being duplicated on the Contributions page in case of quick switch between the Summary and Detailed views.

Multi-select filter for teams and users on the People page

In this version, we've added the capability to select multiple teams and users on the People page, separately and combined, to filter the results shown on the page, making it easier to analyze the activity of individual users and teams on the global level.

The new filtering options also apply to the Export to CSV feature and will be reflected in the resulting CSV file.

Multi-select filter for teams and users on the People page

In this version, we've added the capability to select multiple teams and users on the People page, separately and combined, to filter the results shown on the page, making it easier to analyze the activity of individual users and teams on the global level.

The new filtering options also apply to the Export to CSV feature and will be reflected in the resulting CSV file.

In this version, we've added the capability to select multiple repositories in the Graphs on the project level to filter the results shown on the page. Using the new checkbox Repositories menu, you can monitor and analyze two or more repos at the same time without having to click through each one.

Compatibility Changes

We've added support for Bitbucket 8.0. Also, beginning with this version, the minimum version of Bitbucket our app is compatible with is version 6.7.0. Limiting the compatibility with the older Bitbucket versions will allow us to provide a better stability of the app on the actual Bitbucket versions and deliver new functionality faster.

In this version, we've added the capability to select multiple repositories in the Graphs on the project level to filter the results shown on the page. Using the new checkbox Repositories menu, you can monitor and analyze two or more repos at the same time without having to click through each one.

Compatibility Changes

We've added support for Bitbucket 8.0. Also, beginning with this version, the minimum version of Bitbucket our app is compatible with is version 6.7.0. Limiting the compatibility with the older Bitbucket versions will allow us to provide a better stability of the app on the actual Bitbucket versions and deliver new functionality faster.

Fixed in this release

• Fixed the XSS vulnerability in the Administration page.

Fixed in this release

• Fixed the XSS vulnerability in the Administration page.

In this version, we've added the capability to select multiple teams and users in the Graphs, separately and combined, to filter the results shown on the pages. The users are selected from the list of Bitbucket users who have read access to the current repository or project.

In this version, we've added the capability to select multiple teams and users in the Graphs, separately and combined, to filter the results shown on the pages. The users are selected from the list of Bitbucket users who have read access to the current repository or project.

• The app adopts the US decimal notation and will use a comma to separate groups of thousands in numbers.

Fixed in this release

• Improved behavior of the internal REST and Servlet endpoints to respond with HTTP 404 in case of URL manipulations with the non-existing project, repo, or username parameter values.
• The issue with redirecting to a non-existent page after login via a direct link to an app's page into an instance whose base URL had a context path, e.g., https://company.com/bitbucket, where /bitbucket is a context path.

• The app adopts the US decimal notation and will use a comma to separate groups of thousands in numbers.

Fixed in this release

• Improved behavior of the internal REST and Servlet endpoints to respond with HTTP 404 in case of URL manipulations with the non-existing project, repo, or username parameter values.
• The issue with redirecting to a non-existent page after login via a direct link to an app's page into an instance whose base URL had a context path, e.g., https://company.com/bitbucket, where /bitbucket is a context path.

In this version, we've added the capability to select multiple teams to include in the Reports, which allows you to get summarized statistics for several teams working in the same repository or project.

Fixed in this release

• Fixed the issue with inaccurate repository search results in the repository filter in the Graphs on project level.
• Fixed the issue causing improper display of the multi-select filter in the Contributions Report in Safari and Internet Explorer 11.

In this version, we've added the capability to select multiple teams to include in the Reports, which allows you to get summarized statistics for several teams working in the same repository or project.

Fixed in this release

• Fixed the issue with inaccurate repository search results in the repository filter in the Graphs on project level.
• Fixed the issue causing improper display of the multi-select filter in the Contributions Report in Safari and Internet Explorer 11.

Fixed in this release

• Reduced the loading time of the user profile page by removing unnecessary databases queries when the app resolves users' aliases.
• Fixed the issue with the total lines of code marker displayed out of the line in the Code Frequency graph.

Fixed in this release

• Reduced the loading time of the user profile page by removing unnecessary databases queries when the app resolves users' aliases.
• Fixed the issue with the total lines of code marker displayed out of the line in the Code Frequency graph.

New in this release

Beginning with this version, the app compatibility changes to support only Bitbucket version 6.2 or higher. We have certain app UI changes planned shortly, and limiting the compatibility with the older Bitbucket versions will allow us to deliver new functionality faster.

Other updates in this release

• We've changed the drop-down pull request state filter to a multi-select filter in Contributions Report, making selecting more than one option easier and less confusing.
• The app color palettes are updated in accordance with Atlassian Design Guidelines.
• The pull request activity in a user Contributions profile is now also available for unlicensed users.
• We've disabled the Commit graph in favor of Bitbucket's standard graph. To see the standard graph, please find the feature.commit.graph parameter in bitbucket.properties file, set it to true and restart the instance. You can find more details in the documentation.

New in this release

Beginning with this version, the app compatibility changes to support only Bitbucket version 6.2 or higher. We have certain app UI changes planned shortly, and limiting the compatibility with the older Bitbucket versions will allow us to deliver new functionality faster.

Other updates in this release

• We've changed the drop-down pull request state filter to a multi-select filter in Contributions Report, making selecting more than one option easier and less confusing.
• The app color palettes are updated in accordance with Atlassian Design Guidelines.
• The pull request activity in a user Contributions profile is now also available for unlicensed users.
• We've disabled the Commit graph in favor of Bitbucket's standard graph. To see the standard graph, please find the feature.commit.graph parameter in bitbucket.properties file, set it to true and restart the instance. You can find more details in the documentation.

REST API: retrieve a list of files with LOC changed in a commit

In this release, we've extended the REST API resource to retrieve data for a single commit, so now it also returns a list of files changed in a commit with the number of lines of code added and deleted in each file.

By default, the data returned by resource includes:

• number of lines of code added and deleted in a commit
• author details
• commit creation time
• parent commits' hashes

But if you use the withFiles query parameter set to TRUE, it will also return the following data:

• files changed in a commit
• number of lines of code added and deleted in each file

Learn more about the resource.

REST API: retrieve a list of files with LOC changed in a commit

In this release, we've extended the REST API resource to retrieve data for a single commit, so now it also returns a list of files changed in a commit with the number of lines of code added and deleted in each file.

By default, the data returned by resource includes:

• number of lines of code added and deleted in a commit
• author details
• commit creation time
• parent commits' hashes

But if you use the withFiles query parameter set to TRUE, it will also return the following data:

• files changed in a commit
• number of lines of code added and deleted in each file

Learn more about the resource.

New in this release

We have restructured the database indexing by adding a new database index to the table which contains commits, so the data provided by the app will display faster after re-indexing. 

The re-indexing and the creation of a new index will take some time and additional storage space on the database host. The re-indexing time estimate is around 0,7-1 second per million of commits:

• Postgres: 1.48 seconds for 2 million commits.
• MS SQL: 9.6 seconds for 14 million commits.

The storage space after re-indexing is estimated to grow 6-8% from the current size. The total storage space can be calculated using the formulas on this page. 

To find out how many commits are in the index, go to Bitbucket Administration → Troubleshooting and support tools → System Information → Awesome Graphs. Learn more on this page.

Fixed in this release

• The issue with a set time period drop when switching between the Summary view and the Detailed view in the Contribution Calendar.

New in this release

We have restructured the database indexing by adding a new database index to the table which contains commits, so the data provided by the app will display faster after re-indexing. 

The re-indexing and the creation of a new index will take some time and additional storage space on the database host. The re-indexing time estimate is around 0,7-1 second per million of commits:

• Postgres: 1.48 seconds for 2 million commits.
• MS SQL: 9.6 seconds for 14 million commits.

The storage space after re-indexing is estimated to grow 6-8% from the current size. The total storage space can be calculated using the formulas on this page. 

To find out how many commits are in the index, go to Bitbucket Administration → Troubleshooting and support tools → System Information → Awesome Graphs. Learn more on this page.

Fixed in this release

• The issue with a set time period drop when switching between the Summary view and the Detailed view in the Contribution Calendar.

Fixed in this release

• The issue with the app failing to display the second and following batches of user cards in the Contributors graph set to Days on large projects.
• Minor issues in the UI caused by the Bitbucket 7.13 update.

Fixed in this release

• The issue with the app failing to display the second and following batches of user cards in the Contributors graph set to Days on large projects.
• Minor issues in the UI caused by the Bitbucket 7.13 update.

Fixed in this release

• The issue with the People page showing irrelevant users and incorrect numbers of pull requests in developer cards.

Fixed in this release

• The issue with the People page showing irrelevant users and incorrect numbers of pull requests in developer cards.

New in this release

Added support for Bitbucket Data Center and Server 7.13.

New in this release

Added support for Bitbucket Data Center and Server 7.13.

Fixed in this release

• The issue with indexing failing on forks not synced with an upstream repo via `git alternates` when `git alternates` is disabled in Bitbucket by setting plugin.bitbucket-git.forks.usealternates=false in $BITBUCKET_HOME/shared/bitbucket.properties.
• The incorrect subscription expiration date displayed on the user's Contributions page.

Fixed in this release

• The issue with indexing failing on forks not synced with an upstream repo via `git alternates` when `git alternates` is disabled in Bitbucket by setting plugin.bitbucket-git.forks.usealternates=false in $BITBUCKET_HOME/shared/bitbucket.properties.
• The incorrect subscription expiration date displayed on the user's Contributions page.

New Date Format

Beginning with this version, the ISO 8601 international date and time format is applied to all dates in data exported to CSV. This update might become a breaking change if you use CSV format in your automations, so If you need help in adapting your scripts to the new format, please write about it in our Help Center.

Pull Request Reviewers

We extended the data exported via Export to CSV by adding two columns for pull requests, showing the users who participated in code review:

• Reviewers' Names
• Reviewers' Usernames

If nobody participated in the review, the cells left blank.

Commit Creation Date

We also added a column with the commit creation date to the commit report, allowing for a more precise analysis of your codebase, as well as further aggregation and visualization.

Learn more about Export to CSV

New Date Format

Beginning with this version, the ISO 8601 international date and time format is applied to all dates in data exported to CSV. This update might become a breaking change if you use CSV format in your automations, so If you need help in adapting your scripts to the new format, please write about it in our Help Center.

Pull Request Reviewers

We extended the data exported via Export to CSV by adding two columns for pull requests, showing the users who participated in code review:

• Reviewers' Names
• Reviewers' Usernames

If nobody participated in the review, the cells left blank.

Commit Creation Date

We also added a column with the commit creation date to the commit report, allowing for a more precise analysis of your codebase, as well as further aggregation and visualization.

Learn more about Export to CSV

Fixed in this release

Tabs displaying on the Graphs page on the displays with low resolution (1344х840 and less) could be broken.

Fixed in this release

Tabs displaying on the Graphs page on the displays with low resolution (1344х840 and less) could be broken.

REST API: retrieve single commit data

In this release, we've added a new REST API resource to retrieve data for a single commit identified by its ID, which allows for a more precise analysis of your codebase. The data returned includes lines of code added and deleted, author details, commit creation time, parent commits' hashes.

Read more about the resource.

Security Improvement

To improve the overall security we disable our graphs on public repositories for anonymous users. Now the app features are only available to authorized Bitbucket users.

REST API: retrieve single commit data

In this release, we've added a new REST API resource to retrieve data for a single commit identified by its ID, which allows for a more precise analysis of your codebase. The data returned includes lines of code added and deleted, author details, commit creation time, parent commits' hashes.

Read more about the resource.

Security Improvement

To improve the overall security we disable our graphs on public repositories for anonymous users. Now the app features are only available to authorized Bitbucket users.

REST API: Export to CSV

In this release, we've added new REST API resources allowing you to export raw data with commits or pull requests statistics to a CSV file.

Using these resources, you can get lists of commits or pull requests with their details, made during the selected period on global, project, repository, and user levels.

Read more about the available REST API resources.

REST API: Export to CSV

In this release, we've added new REST API resources allowing you to export raw data with commits or pull requests statistics to a CSV file.

Using these resources, you can get lists of commits or pull requests with their details, made during the selected period on global, project, repository, and user levels.

Read more about the available REST API resources.

New in this release

We've added the Timeout status for repositories that we failed to index for 16 hours. This time limit is currently set to avoid the endless processing of a single repository.

Before that, we marked those repositories with the Invalid status which led to new attempts to re-index them after re-enabling the app. Now, these repositories will not be processed after re-enabling the app to reduce the performance impact and increase the indexing speed.

Same as before, you may find the status of indexing on your instance in Bitbucket Administration > Troubleshooting and support tools > System Information > Awesome Graphs or in the awesome-graphs.log file located in /log.

New in this release

We've added the Timeout status for repositories that we failed to index for 16 hours. This time limit is currently set to avoid the endless processing of a single repository.

Before that, we marked those repositories with the Invalid status which led to new attempts to re-index them after re-enabling the app. Now, these repositories will not be processed after re-enabling the app to reduce the performance impact and increase the indexing speed.

Same as before, you may find the status of indexing on your instance in Bitbucket Administration > Troubleshooting and support tools > System Information > Awesome Graphs or in the awesome-graphs.log file located in <Bitbucket home directory>/log.

Fixed in this release

The issue with the long indexing of the annotated tag if it was previously put in the indexing queue, but removed from the repository before the app started processing it.

Fixed in this release

The issue with the long indexing of the annotated tag if it was previously put in the indexing queue, but removed from the repository before the app started processing it.

New in this release 

Included the Cache-Control and X-Frame-Options HTTP headers in the endpoint's responses to provide better security.

New in this release 

Included the Cache-Control and X-Frame-Options HTTP headers in the endpoint's responses to provide better security.

Fixed in this release

When creating annotated tags in repo via REST API, Bitbucket UI, or git tag command, the indexator used to include the tag's hash, instead of the hash of commit the tag was referring to. As a result, indexation in repositories with many commits could take a long time to complete.

Fixed in this release

When creating annotated tags in repo via REST API, Bitbucket UI, or git tag command, the indexator used to include the tag's hash, instead of the hash of commit the tag was referring to. As a result, indexation in repositories with many commits could take a long time to complete.

Fixed in this release

We've made some indexing optimization for faster processing and added more informative logging. 

Fixed in this release

We've made some indexing optimization for faster processing and added more informative logging. 

REST API: Pull Requests Details 

In this release, we've added the capability to export the data with the detailed list of pull requests with their metadata via the REST API endpoints.

Awesome Graphs' REST API provides global, user, project, and repository data, outperforming the Bitbucket's REST API. 

Awesome Graphs' REST APIs provide access to resources (data entities) via URI paths. To use REST API, your application will make an HTTP request and parse the response. Read more.

The Contributions Report: Filtering by State

We've also added the possibility to choose multiple options of filtering by state in the Contributions report to capture trends of developers' involvement in the code review. Before that, it was only possible to select either pull requests of one state or all of them.

Fixed in this release

• optimization of the indexing process to decrease the indexing time while pushing new branches
• ISO date format while exporting to CSV
• some stored XSS vulnerabilities.

REST API: Pull Requests Details 

In this release, we've added the capability to export the data with the detailed list of pull requests with their metadata via the REST API endpoints.

Awesome Graphs' REST API provides global, user, project, and repository data, outperforming the Bitbucket's REST API. 

Awesome Graphs' REST APIs provide access to resources (data entities) via URI paths. To use REST API, your application will make an HTTP request and parse the response. Read more.

The Contributions Report: Filtering by State

We've also added the possibility to choose multiple options of filtering by state in the Contributions report to capture trends of developers' involvement in the code review. Before that, it was only possible to select either pull requests of one state or all of them.

Fixed in this release

• optimization of the indexing process to decrease the indexing time while pushing new branches
• ISO date format while exporting to CSV
• some stored XSS vulnerabilities.

REST API: Pull Requests Statistics

In this release, we've added the capability to export the data with the pull requests statistics via the REST API endpoints, so now you can get the number of pull requests on global, user, project, and repository level, grouped by their state, with speed outperforming the Bitbucket's REST API.

Read more about the REST API Pull Requests resources .

Export to CSV: Last Updated Date value for Pull Requests lists

We have also increased the detalization of the data exported via the Export to CSV feature by adding the "Last Updated Date" value to the list of pull requests, which lets you

• see the Resolution Time and monitor pull requests' health
• find the pull requests that got stuck and address timely
• Integrate with BI tools and Analytics solutions and build real-time dashboards.

Read more about exporting your data to CSV files.

REST API: Pull Requests Statistics

In this release, we've added the capability to export the data with the pull requests statistics via the REST API endpoints, so now you can get the number of pull requests on global, user, project, and repository level, grouped by their state, with speed outperforming the Bitbucket's REST API.

Read more about the REST API Pull Requests resources .

Export to CSV: Last Updated Date value for Pull Requests lists

We have also increased the detalization of the data exported via the Export to CSV feature by adding the "Last Updated Date" value to the list of pull requests, which lets you

• see the Resolution Time and monitor pull requests' health
• find the pull requests that got stuck and address timely
• Integrate with BI tools and Analytics solutions and build real-time dashboards.

Read more about exporting your data to CSV files.

Fixed in this release

On Bitbucket versions from 7.0 and above, the Contributions report could display incorrect results if it was grouped by tasks. Other grouping options worked correctly.

We also fixed an issue that occurred on a database due to the processing of the contributors' names longer than 255 symbols.

Fixed in this release

On Bitbucket versions from 7.0 and above, the Contributions report could display incorrect results if it was grouped by tasks. Other grouping options worked correctly.

We also fixed an issue that occurred on a database due to the processing of the contributors' names longer than 255 symbols.

REST API: Commits

In this release, we've added the capability to export the data with the detailed list of commits and statistics in terms of lines of code via the REST API endpoints.

Awesome Graphs' REST API provides global, user, project, and repository data. Our solution allows you to retrieve data faster while decreasing the load on the instance compared to Bitbucket's REST API.

Using the REST API feature you can:

• integrate with analytics platforms and extend their capabilities with live access to data provided by Awesome Graphs
• build custom graphs, aggregate, sort and filter the data in Excel, Tableau, Google Spreadsheets, and other tools
• create live-dashboards for real-time monitoring
• merge data from Awesome Graphs, Jira and other sources to enable end-to-end visibility reports for management.

Read more about the Awesome Graphs REST API resources.

REST API: Commits

In this release, we've added the capability to export the data with the detailed list of commits and statistics in terms of lines of code via the REST API endpoints.

Awesome Graphs' REST API provides global, user, project, and repository data. Our solution allows you to retrieve data faster while decreasing the load on the instance compared to Bitbucket's REST API.

Using the REST API feature you can:

• integrate with analytics platforms and extend their capabilities with live access to data provided by Awesome Graphs
• build custom graphs, aggregate, sort and filter the data in Excel, Tableau, Google Spreadsheets, and other tools
• create live-dashboards for real-time monitoring
• merge data from Awesome Graphs, Jira and other sources to enable end-to-end visibility reports for management.

Read more about the Awesome Graphs REST API resources.

Fixed in this release

On Bitbucket instances with a large number of repositories (5,000 and more) where MS SQL is used as a database, there could be some issues with repositories indexing while updating the app due to the fully filled transaction log in the database.

Fixed in this release

On Bitbucket instances with a large number of repositories (5,000 and more) where MS SQL is used as a database, there could be some issues with repositories indexing while updating the app due to the fully filled transaction log in the database.

Fixed in this release

• The issue with the missing Add yourself as a reviewer button in Bitbucket v.7.1.0 and 7.1.1.

Fixed in this release

• The issue with the missing Add yourself as a reviewer button in Bitbucket v.7.1.0 and 7.1.1.

Reports for teams

In this release, we added the ability of watching pull requests and commits reports for teams. Using this feature, you can:

• analyze code review processes of a single team, excluding contributors from the others
• compare the statistics for pull requests of several teams
• exclude the data added by automated users from reports.

Before that, it was only possible to see the team's statistics on the Graphs page. Read more about teams here.

Also in this release

• Fixed the issue that occurred while watching the Pie Chart report grouped by author or reviewer when there're more than 1000 users to display. Errors happened in Bitbucket instances with the Oracle database.
• Changed column names in exported CSV files. We replaced the User Display Name with the Author Name, and the Bitbucket Username with the Author Username columns in the lists of commits to make them similar to the lists of pull requests exported to CSV.

Reports for teams

In this release, we added the ability of watching pull requests and commits reports for teams. Using this feature, you can:

• analyze code review processes of a single team, excluding contributors from the others
• compare the statistics for pull requests of several teams
• exclude the data added by automated users from reports.

Before that, it was only possible to see the team's statistics on the Graphs page. Read more about teams here.

Also in this release

• Fixed the issue that occurred while watching the Pie Chart report grouped by author or reviewer when there're more than 1000 users to display. Errors happened in Bitbucket instances with the Oracle database.
• Changed column names in exported CSV files. We replaced the User Display Name with the Author Name, and the Bitbucket Username with the Author Username columns in the lists of commits to make them similar to the lists of pull requests exported to CSV.

New in this release:

• Added support for Bitbucket Server and Data Center 7.0.

New in this release:

• Added support for Bitbucket Server and Data Center 7.0.

Fixed in this release

The issue with the File Contributors drop-down menu in large repositories when there are short hashes that exist twice or more times for different commits in it.

Fixed in this release

The issue with the File Contributors drop-down menu in large repositories when there are short hashes that exist twice or more times for different commits in it.

Fixed in this release

The performance issue when the repository indexing failed if there were commits that include changes to millions of files.

Fixed in this release

The performance issue when the repository indexing failed if there were commits that include changes to millions of files.

Fixed in this release

Issue when the Teams page in Administration wasn't displayed when the Bitbucket URL had a context path.

Fixed in this release

Issue when the Teams page in Administration wasn't displayed when the Bitbucket URL had a context path.

Fixed in this release:

• In the Lines of code page in repository settings, there was a missing field for adding patterns to exclude files from lines of code statistics. This issue appeared in 4.9.0 and higher versions of the app.
• After changing a branch on the Graphs page, pressing the Back button did not lead to the previous branch.
• Incorrect Activity Stream in the Activity graph displaying when a high-resolution picture is included in a pull request description.

Fixed in this release:

• In the Lines of code page in repository settings, there was a missing field for adding patterns to exclude files from lines of code statistics. This issue appeared in 4.9.0 and higher versions of the app.
• After changing a branch on the Graphs page, pressing the Back button did not lead to the previous branch.
• Incorrect Activity Stream in the Activity graph displaying when a high-resolution picture is included in a pull request description.

Fixed in this release:

• Contributions Report: both open and merged pull requests displayed when the report was filtered by merged ones.
• Resolution Time Distribution Report: when hovering over a bar, a hint showed an incorrect resolution time of pull requests.

Fixed in this release:

• Contributions Report: both open and merged pull requests displayed when the report was filtered by merged ones.
• Resolution Time Distribution Report: when hovering over a bar, a hint showed an incorrect resolution time of pull requests.

ⓘ After updating to 5.0.0 complete re-indexing of commit data will take place. It is recommended to schedule the update onto off-hours.

✅Exporting to CSV

In this release, we've added the possibility to export the raw data with the list of commits or pull requests and their details from the People page to a CSV file. You may use this feature to:

• Create custom graphs and apply different filters and sorting options in Excel, Tableau, etc.
• Integrate it to your analytics tool (e.g., Tableau, Grafana, Power BI) to identify trends in comparison with the data from Jira and other sources
• Get the number of lines of code added and deleted by a user across all projects and repositories
• Create a report based on the developers' activity to share it with stakeholders

✅Fixes in commits indexing after rewriting the Git history

We've changed the process of indexing to adjust it to the consequences of deleting branches or rewriting the Git history with such commands as git rebase, force push, and so on.

ⓘ After updating to 5.0.0 complete re-indexing of commit data will take place. It is recommended to schedule the update onto off-hours.

✅Exporting to CSV

In this release, we've added the possibility to export the raw data with the list of commits or pull requests and their details from the People page to a CSV file. You may use this feature to:

• Create custom graphs and apply different filters and sorting options in Excel, Tableau, etc.
• Integrate it to your analytics tool (e.g., Tableau, Grafana, Power BI) to identify trends in comparison with the data from Jira and other sources
• Get the number of lines of code added and deleted by a user across all projects and repositories
• Create a report based on the developers' activity to share it with stakeholders

✅Fixes in commits indexing after rewriting the Git history

We've changed the process of indexing to adjust it to the consequences of deleting branches or rewriting the Git history with such commands as git rebase, force push, and so on.

We've fixed an issue in the All contributors drop-down list on the Graphs page. It caused the situation when users could see the contributors from other repositories of the project to which they didn't have access. Now users can see only those contributors who committed to those repositories from the project that are visible for them.

We also added compatibility with SVN Mirror for Bitbucket Server. It gives the ability to view commits of all branches in the Commits tab.

We've fixed an issue in the All contributors drop-down list on the Graphs page. It caused the situation when users could see the contributors from other repositories of the project to which they didn't have access. Now users can see only those contributors who committed to those repositories from the project that are visible for them.

We also added compatibility with SVN Mirror for Bitbucket Server. It gives the ability to view commits of all branches in the Commits tab.

• The search by author tab in the Top Committers Report was not working;
• In public repositories, the Contributors graph for unauthorized users wasn't displayed.

• The search by author tab in the Top Committers Report was not working;
• In public repositories, the Contributors graph for unauthorized users wasn't displayed.

We added support for Bitbucket 6.8.

Awesome Graphs is now compatible with the new Content Delivery Network (CDN) feature for Bitbucket Data Center. CDN helps to increase the speed of the page load by serving static assets from servers closer to users, which is mostly helpful for those teams who are distributed in different time zones.

We added support for Bitbucket 6.8.

Awesome Graphs is now compatible with the new Content Delivery Network (CDN) feature for Bitbucket Data Center. CDN helps to increase the speed of the page load by serving static assets from servers closer to users, which is mostly helpful for those teams who are distributed in different time zones.

Fixed in this release

We've changed the way the commits are displayed in the Commits graph while watching it for all branches together. Before that, it showed the commits in the topological order and we changed it to the date order to display commits chronologically.

Fixed in this release

We've changed the way the commits are displayed in the Commits graph while watching it for all branches together. Before that, it showed the commits in the topological order and we changed it to the date order to display commits chronologically.

In this release, it became possible to create teams and watch graphs for them for a more precise analysis. That is especially useful for the projects or repositories with multiple teams working on it:

• to watch graphs for a single team and exclude contributors from the others;
• to compare the activity of different teams;
• to create the preset of filters with a different combination of contributors.

This version includes graphs for teams on the Graphs page. Teams for the Reports page and the People page will be available in the next releases. Read more about teams here.

Teams can be created on the global, project or repository level and include Bitbucket users and groups.

In this release, it became possible to create teams and watch graphs for them for a more precise analysis. That is especially useful for the projects or repositories with multiple teams working on it:

• to watch graphs for a single team and exclude contributors from the others;
• to compare the activity of different teams;
• to create the preset of filters with a different combination of contributors.

This version includes graphs for teams on the Graphs page. Teams for the Reports page and the People page will be available in the next releases. Read more about teams here.

Teams can be created on the global, project or repository level and include Bitbucket users and groups.

We've redesigned the People page: changed the interface and added the possibility to choose a custom period of time within the past 30 days for a more precise analysis.

Besides, Awesome Graphs is now compatible with Bitbucket Server 6.7.

We've redesigned the People page: changed the interface and added the possibility to choose a custom period of time within the past 30 days for a more precise analysis.

Besides, Awesome Graphs is now compatible with Bitbucket Server 6.7.

Fixed in this release:

• The issue when deleting a group from a user's membership list led to the deletion of this group from Bitbucket.

Fixed in this release:

• The issue when deleting a group from a user's membership list led to the deletion of this group from Bitbucket.

We have improved the Activity Stream with the list of commits and pull requests. Now, it's possible to see more details of the project, repository or user activity:

• what project a pull request or commit belongs to;
• what branch a commit belongs to.

We have improved the Activity Stream with the list of commits and pull requests. Now, it's possible to see more details of the project, repository or user activity:

• what project a pull request or commit belongs to;
• what branch a commit belongs to.

Fixed in this release:

• When trying to change the previously chosen custom time period in the calendar on the Configure page, today's date appeared instead of the chosen before.
• On the Configure page, clicking on the filter title resulted as choosing all items from the list in Internet Explorer.

Fixed in this release:

• When trying to change the previously chosen custom time period in the calendar on the Configure page, today's date appeared instead of the chosen before.
• On the Configure page, clicking on the filter title resulted as choosing all items from the list in Internet Explorer.

In this release, we've added a possibility for Bitbucket administrators to manage email aliases of other users in Bitbucket UI. Before that, managing aliases for administrators and other users was possible via REST API, .mailmap file in the repository or in the user profile.

Learn more

In this release, we've added a possibility for Bitbucket administrators to manage email aliases of other users in Bitbucket UI. Before that, managing aliases for administrators and other users was possible via REST API, .mailmap file in the repository or in the user profile.

Learn more

In this release:

• Increased the timeout of indexing from 4 to 16 hours for correct working with large repositories in Bitbucket Server. The timeout of indexing for Bitbucket Data Center remains 16 hours.
• Changed the order of commits displaying in the Commits page from --date-order to --topo-order to prevent situations when children commits in the Commit Graph appear before their parents while watching all branches of the repository using the Show all button.

We've also fixed:

• Incorrect displaying for branch labels in the Commits tab for Bitbucket versions below 5.10
• Issues when the Commit Graph was shown along with inbuilt Bitbucket one after switching from a branch with one commit to a branch with two or more commits.
• A bug in the Graphs page when it was impossible to choose previously displayed branch after clearing the branch filter by clicking the Show all button.

In this release:

• Increased the timeout of indexing from 4 to 16 hours for correct working with large repositories in Bitbucket Server. The timeout of indexing for Bitbucket Data Center remains 16 hours.
• Changed the order of commits displaying in the Commits page from --date-order to --topo-order to prevent situations when children commits in the Commit Graph appear before their parents while watching all branches of the repository using the Show all button.

We've also fixed:

• Incorrect displaying for branch labels in the Commits tab for Bitbucket versions below 5.10
• Issues when the Commit Graph was shown along with inbuilt Bitbucket one after switching from a branch with one commit to a branch with two or more commits.
• A bug in the Graphs page when it was impossible to choose previously displayed branch after clearing the branch filter by clicking the Show all button.

Fixed in this release:

• Issues occurred when trying to watch Graphs and Reports for projects with more than 1000 repositories for Oracle and MSSQL.

Fixed in this release:

• Issues occurred when trying to watch Graphs and Reports for projects with more than 1000 repositories for Oracle and MSSQL.

In this release:

• We've fixed an issue when it was impossible to add an email alias to a user which username was same to an added email alias.
• The add-on is now compatible with Bitbucket Server versions from 5.1 and above.

In this release:

• We've fixed an issue when it was impossible to add an email alias to a user which username was same to an added email alias.
• The add-on is now compatible with Bitbucket Server versions from 5.1 and above.

Fixed in this release:

• Incorrect displaying of the long contributor's username in the Contributors graph;
• Issues with the date selector and users' graphs duplicating in the Contributors graph;
• Errors occurred while the commit indexing if commits were made by a contributor whose name or email contained one or more newlines;
• Displaying of the "All repositories" button in the Repositories filter on the Contributions graph in the user profile;
• Repository/branch selectors did not display more than 37 repositories/branches in the Graphs page.

Fixed in this release:

• Incorrect displaying of the long contributor's username in the Contributors graph;
• Issues with the date selector and users' graphs duplicating in the Contributors graph;
• Errors occurred while the commit indexing if commits were made by a contributor whose name or email contained one or more newlines;
• Displaying of the "All repositories" button in the Repositories filter on the Contributions graph in the user profile;
• Repository/branch selectors did not display more than 37 repositories/branches in the Graphs page.

In this release:

• Fixed a bug with viewing graphs for a project on Bitbucket 6.2.0.
• Improved compatibility with MS Team Connector add-on.
• Fixed a problem with commit indexing for Bitbucket Data Center which happened while pushing from several nodes to the same Git repository.

In this release:

• Fixed a bug with viewing graphs for a project on Bitbucket 6.2.0.
• Improved compatibility with MS Team Connector add-on.
• Fixed a problem with commit indexing for Bitbucket Data Center which happened while pushing from several nodes to the same Git repository.

New in this release:

• Improved logging messages in the awesome-graphs.log file.
• All compatibility issues with Bitbucket 6.0 and Bitbucket 6.1 have finally been resolved.

New in this release:

• Improved logging messages in the awesome-graphs.log file.
• All compatibility issues with Bitbucket 6.0 and Bitbucket 6.1 have finally been resolved.

New in this release:

• Exclusion of files from lines of code statistics.
• Improvements in the repository selector in the Contributions graph.

Now it is possible to exclude files from lines of code statistics shown in the Contributors graph and the Code Frequency graph.

Users can enter patterns in .gitignore format telling what files and directories should be excluded from lines of code statistics of the repository. It is also possible to include only files with selected extensions or from selected folders (and exclude all other files).

This feature will help users to get more accurate lines of code statistics if they don't want to count third-party libraries, documents, or automatically generated files (i.e. generated Perl modules that are created from examining the database schema).

Learn more

New in this release:

• Exclusion of files from lines of code statistics.
• Improvements in the repository selector in the Contributions graph.

Now it is possible to exclude files from lines of code statistics shown in the Contributors graph and the Code Frequency graph.

Users can enter patterns in .gitignore format telling what files and directories should be excluded from lines of code statistics of the repository. It is also possible to include only files with selected extensions or from selected folders (and exclude all other files).

This feature will help users to get more accurate lines of code statistics if they don't want to count third-party libraries, documents, or automatically generated files (i.e. generated Perl modules that are created from examining the database schema).

Learn more

Fixed in this release:

• Names of Git contributors with Unicode symbols were displayed incorrectly.

Fixed in this release:

• Names of Git contributors with Unicode symbols were displayed incorrectly.