Skip to content

[Spike] Unify fetching filter token suggestions using Apollo

What does this MR do and why?

Move fetching filter token suggestions to Token components and use GraphQl and Apollo when available on the backend

  • MilestoneToken
  • UserToken
  • LabelToken

Impact issues and epic boards, issues lists, epic lists and epic roadmap.

Existing passed fetch functions through token config are still used as fallback for areas of the product where the migration has not happened yet (e.g. cycle analytics, issues dashboard...)

Screenshots or screen recordings

No user facing changes.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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 #392982 (closed)

Edited by Florie Guibert

Merge request reports