When Jira Issues are fetched, we ask Jira (with new requests) what name the user (that is only mentioned by their slug in the jira description / comments...) actually has so we can replace that with the users name. This causes a lot of requests each time we refresh the tickets.
We should cache that information in the local storage, some sort of map of the slug -> user name that we resolve with requests. So if there is a hit, we do not need to fetch that information from Jira again. This will save us a lot of requests to Jira.
When Jira Issues are fetched, we ask Jira (with new requests) what name the user (that is only mentioned by their slug in the jira description / comments...) actually has so we can replace that with the users name. This causes a lot of requests each time we refresh the tickets.
We should cache that information in the local storage, some sort of map of the slug -> user name that we resolve with requests. So if there is a hit, we do not need to fetch that information from Jira again. This will save us a lot of requests to Jira.