Inconsistency observed in the Burndown Chart report custom field value changes which having translation configured.

Issue Summary

This is reproducible on Data Center: (yes) / (no) Yes

For custom fields that have language translation configured, inconsistency is observed in the changes made to the custom field in the Burndown Chart. For example, if the custom field has translation configured for Spanish, a user using the Spanish language only sees the changes made to the custom field while in the Spanish language in the burndown chart, they cannot see the changes made to the same custom field by another user who has made changes while using the English language.

Steps to Reproduce

1. Create a custom field(type: number field) ex: test_translation, configure a translation for this custom field. (Issues -> custom field -> "test_translation -> "..." translate)
   
2. Add the Custom Field to a test project.
3. While using "English" as language preference in User profile, make changes to custom field i.e "test_translation".
4. Now, switch the language to "Spanish" from the User profile's language preferences.
5. While using "Spanish" as language preference in User profile, make changes to custom field i.e "spanio".
6.  In the Issue, History, we can see the changes made in both the lanuguages.
   

Expected Results

In the Burndown chart, all the changes made to the custom fields need to be visible irrespective of the language in which the change was made.

Actual Results

However, In the Burndown chart, changes made to the custom field in Spanish appear while using Spanish, likewise, changes made in English appear only while using English language preference in the user profile.

Burndown chart while User profile in Spanish

Burndown chart while User profile in English

Workaround

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