Tags are missing in the Commit listing page in Bitbucket Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Git Tags are missing on the Commit list page in Bitbucket. But, if you navigate inside the Commit the tags do appear correctly on the individual Commit's page.
Environment
Bitbucket 9.4.X and 8.19.X, though this may occur on other versions.
Cause
If a single commit has more than 500 tags assigned to it, the tags will not display on the Commits list page.
Only the first 500 tags are fetched in an alphabetical order and displayed as (9+ tags ) icon on the UI. The limitation is intentional, and was put in place to avoid overload of browser and server resources.
Solution
Manually increase tag limit
Increasing the max tags value may increase demand on both the browser and Bitbucket server during page render. Values that are too large might lead to decreased performance or other undesirable side effects. We highly recommend you adjust this setting on your test instance before implementing a change to a live production environment.
To increase the display limit for the tags in the application, add following configuration parameter to the bitbucket.properties located at $BITBUCKET_HOME/shared directory. Save this file by adding the property and restart the application to reflect the changes.
plugin.tag.index.page.max.tags=500500 is the default limit of tags fetched on commits page. The parameter value can be increased based on the use case. When the value is increased to 1000, the application will retrieve the first 1000 tags in alphabetical order. If there are more than 1000 tags on a single commit, the same behavior as described above will continue to occur.
Was this helpful?