Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
Context: in the report definition, frontend requires a proper user's display name for readability, and while preparing the REST response in the backend, we resolve the owner's and last modifier's IDs to display names. However, sometimes we try to resolve the names with the IDs provided back from frontend (the actual display names), which leads to cache misses and subsequent 429 too many request failures.
We implemented a temporary workaround for the release.
We have to properly implement the userID/display name handling to avoid cache misses and potential authorization issues.
Testing Notes:
- Unsaved report evaluation works as expected. Do some regression around evaluating unsaved reports and evaluating saved reports
- Regression around any representation of owner or last modified displayed in the UI relating to unsaved reports