Resolve "API cache not getting invalidated when using /reassign in merge request"

Marc Shawrequested to merge
364264-api-cache-not-getting-invalidated-when-using-reassign-in-merge-request into master

What does this MR do and why?

Add reviewers and assignees to the cache key - so that the cache is updated, if either of these are updated.

Steps to reproduce

  • Create a merge request
  • Check through the API api/v4/projects/2/merge_requests?state=opened
  • use /reassign to assign someone
  • Check through the API again.
  • The api should have the new assignees

Related to #364264 (closed)

Edited by Marc Shaw

Merge request reports