Issue Summary

Comments reactions were introduced on Jira 8.18.

When an issue has a comment, Jira UI requires additional data to load reaction components, such as the below.
Details about the available reactions are provided as the result of the request to GET /rest/internal/2/reactions/emojis.

If the same issue has multiple comments, then Jira will trigger the same request multiple times, one for each comment.
Since the request and the response is exactly the same, this may be unnecessary.

The problem may be minimized on a production instance as the request may be cached on the user browser.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This was validated on Jira SW DC versions 8.20.30, 9.12.12 and 10.0.0.
2. Create a project with sample data.
3. Create a Jira issue and load it on the browser.
   • Note no GET /rest/internal/2/reactions/emojis are made as there's no comment.
4. Add a comment to this Jira issue and reload it.
   • Note one request is made to GET /rest/internal/2/reactions/emojis, which loads metadata about available reactions that can be added to a comment.
5. Add another comment to the same Jira issue and reload it.

Expected Results

Since any comment's reactions rely on the same metadata, only a single request to GET /rest/internal/2/reactions/emojis is made.

Actual Results

Two requests are made to GET /rest/internal/2/reactions/emojis.

The more comments an issue has, more requests are made to same endpoint.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.