Avoid N+1 query on root level issues query
What does this MR do and why?
4th MR related to adding coverage for the new root level issues
query. Before we only had an issues query scoped to a project project.issues
. Because of issues would belong to the same project, we wouldn't get an N+1 query when authorizing each issue. For the new query, if an issue belongs to a different project, it will have to query the DB for the max access level the user has in each project. This MR preloads the max access level in our cache mechanism that uses Redis to store these values
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #377514 (closed)