Adding reaction to comment returns "This comment couldn't be displayed" in Bitbucket
Platform Notice: Data Center Only - This article only applies to Atlassian products 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
Attempting to add an emoticon/reaction to a comment within Bitbucket Server/Data Center (added in Bitbucket 7.7) results in the following error being displayed:
1
2
3
This comment couldn't be displayed
Try reloading the pageAlternatively, when you try to add a reaction, no emoticons/emojis are displayed for selection.
Environment
Bitbucket Data Center 7.7+
Diagnosis
If debug logging has been enabled, the following messages will be present within the application logs:
1
2
2021-08-27 11:25:02,646 DEBUG [http-nio-7990-exec-9] @6N2YO7x685x686x1 2ye2pr 192.168.5.1,192.168.5.2 "GET /mvc/error404 HTTP/1.1" c.a.s.i.web.ErrorPageController Page not found attempting to access [/bitbucket/rest/emoticons/latest/search]
2021-08-27 11:25:02,650 DEBUG [http-nio-7990-exec-6] @6N2YO7x685x687x1 2ye2pr 192.168.5.1,192.168.5.2 "GET /mvc/error404 HTTP/1.1" c.a.s.i.web.ErrorPageController Page not found attempting to access [/bitbucket/rest/emoticons/latest/emoticons]Cause
This behavior is likely due to one or more system plugins being disabled that are related to the ability to add reactions to comments within Bitbucket.
The system apps that, when disabled, cause this error are as follows:
Bitbucket Server - Comment Likes
Bitbucket Server - Emoticons
This can be confirmed by navigating to Administration Menu (top right cog) > Manage Apps > Select 'System' from the dropdown menu and then expanding the plugins mentioned above.
The root cause for why these system plugins would be disabled is not currently known at this time.
Based on the data we have so far, this issue seems to only occur following an update to Bitbucket 7.7 or higher.
It's suspected that if one or more of these system plugins were disabled prior to the update, this would result in the behavior seen here post-update.
Solution
Click the 'Enable' button on each disabled system plugin.
After reloading the affected page, the comment reaction functionality should now be immediately restored.
Was this helpful?