Overview:

A high level summary that describes the Epic in a clear, concise way. Complete during New status.

Remove GraphQL to simplify the maintenance burden of the code base as well as improve performance by reducing back and forth calls with the database.

Requirements:

A list of specific needs or objectives that an epic must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

• Understand the scope and pervasiveness of usage
• Add deprecation notice that the GraphQL endpoints will be removed
• Catalog the current usages of graphql queries
  • including cataloging of fields that are not in use.
• Catalog GraphQL queries that can simply be served by existing APIs
• Catalog GraphQL queries that will need replaced by new APIs
• Design API scheme for the new APIs.
• Implement REST endpoints in a LIFO order relative to recent UI development
• Remove GraphQL from the code base
• Documentation of new APIs

Technical Scope:

High-level list of items that are in scope; usually completed by a staff engineer or a lead from the Feature Delivery Team. Initial completion during Refinement status.

<your text here>

Out of Scope:

High-level list of items that are out of scope. Initial completion during Refinement status.

<your text here>

Outstanding Questions (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.

<your text here>

See  https://docs.google.com/document/d/1kz0u6HaRj6x8I8TIVB8GJT1bQAtXo7m585ytxt-k_IY/edit?usp=sharing