-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Context:
Currently some text that is returned from the BE and displayed in optimize is hardcoded in english but it has to use translations.
AT:
- use X-Optimize-Client-Locale header to get the client locale code for translations
- if the code is unknown/invalid/missing fall back to English
- do the translations for management dashboard and instant preview dashboards
- write unit tests to check the translation files
Testing Notes:
The following endpoints should return localised entity names:
api/dashboard/management
api/report/{reportId}/evaluate
api/dashboard/instant
api/entities/names
This is the controller panel for Smart Panels app
[OPT-6751] Use translations for static content
Status | Original: Triage [ 10612 ] | New: Ready [ 10005 ] |
Assignee | New: Helene Waechtler [ helene.waechtler ] |
Description |
Original:
Context:
Currently some text that is returned from the BE and displayed in optimize is hardcoded in english but it has to use translations. AT: * use *X-Optimize-Client-Locale* header to get the client locale code for translations * if the code is unknown/invalid/missing fall back to English * use the translations for *management dashboard* and *instant preview dashboards* * write unit tests to check the translation files |
New:
Context:
Currently some text that is returned from the BE and displayed in optimize is hardcoded in english but it has to use translations. AT: * use *X-Optimize-Client-Locale* header to get the client locale code for translations * if the code is unknown/invalid/missing fall back to English * do the translations for *management dashboard* and *instant preview dashboards* * write unit tests to check the translation files |
Status | Original: Ready [ 10005 ] | New: In Development [ 10312 ] |
Description |
Original:
Context:
Currently some text that is returned from the BE and displayed in optimize is hardcoded in english but it has to use translations. AT: * use *X-Optimize-Client-Locale* header to get the client locale code for translations * if the code is unknown/invalid/missing fall back to English * do the translations for *management dashboard* and *instant preview dashboards* * write unit tests to check the translation files |
New:
*Context:*
Currently some text that is returned from the BE and displayed in optimize is hardcoded in english but it has to use translations. *AT:* * use *X-Optimize-Client-Locale* header to get the client locale code for translations * if the code is unknown/invalid/missing fall back to English * do the translations for *management dashboard* and *instant preview dashboards* * write unit tests to check the translation files *Testing Notes:* The following endpoints should return localised entity names: {{api/dashboard/management}} {{api/report/\{reportId}/evaluate}} {{api/dashboard/instant}} {{api/entities/names}} |
Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
Hi helene.waechtler,
The instant preview dashboard depends on https://github.com/camunda/product-hub/issues/775 wish is WIP - you can add placeholders for now.
I added my feedback to the sheet you proposed: https://docs.google.com/spreadsheets/d/1y_VKZgijv-_wm-Nalv1wkkLIX30F4Uts_7hjcn8f4Iw/edit#gid=0
Regards Tobias