Skip to content

Expose imported status for relevant entities

Carla Drago requested to merge 424454-expose-imported-state into master

What does this MR do and why

This exposes the imported state for Designs, Epics, Events, Issues, Merge Requests, Notes, and Snippets as a boolean.

This follows MR !149570 (merged) which added an imported column to each resource.

Helpers, models, serializers, api entities, concerns, graphql queries and types have all been updated where necessary.

An ImportSource concern class has been added with methods to:

  • set enum attribute that uses a defined hash, and a prefix;
  • return a boolean.

This work is part of Issue #424454 which will allow these resources to have a visual indicator in the UI to show they have been imported.

A follow-up MR to update each importer to add the enum value to the imported DB column will follow this MR.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

REST API request results

Discussions

discussions

Epics

epics

Events

events

Issues

issues

Merge Requests

merge-requests

Notes

notes

Snippets

snippets

GraphQL request results

Snippets

snippets-graphql

Designs

designs-graphql

How to set up and validate locally

  • Make requests to the endpoints/queries shown in the screenshots above

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

Related to #424454

Edited by Carla Drago

Merge request reports