Skip to content

Avoid N+1 queries in GraphQL WorkItems resolver

What does this MR do and why?

We had multiple N + 1 DB queries when fetching some fields from a work item and using the WorkItemsResolver. THis change adds a way to preload fields that are nested one level deep.

How to set up and validate locally

The best way to test this is via the introduced spec since it only improves performance on how we query the DB.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #365998 (closed)

Edited by Mario Celi

Merge request reports