Draft: WIP: Create Epic with a synched work item on import
What does this MR do and why?
This MR adds the ability to import legacy Epics and their corresponding Epic Work Items into a group.
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.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Explanation of DIFF
The diff introduces a new class called EpicsPipeline
that is responsible for importing legacy Epics and their corresponding Epic Work Items into a group.
The load
method in this class checks if the data is present and if it is, it creates an Epic using the Epics::CreateService
. The service is called using send
to bypass the private method check.
The object_builder
method returns an instance of Gitlab::ImportExport::Group::EpicObjectsBuilder
, which is responsible for building Epic objects.
The work_item_params
method prepares the attributes for creating the Epic Work Item. It includes attributes like title, description, and assignee.
The work_item_attributes
method returns a list of allowed attributes for creating the Epic Work Item.
This description was generated for revision e5959cd2 using AI