Import epic award emojis when using Bulk Import
What does this MR do?
This MR adds migration of epic award emojis when using Bulk Import (GitLab Migration) tool that ~"group::import" has been working on (https://docs.gitlab.com/ee/development/bulk_import.html).
We cannot add emojis to GetEpicsQuery, similar to Labels for example https://gitlab.com/gitlab-org/gitlab/blob/georgekoltsov/group-migration-epic-award-emoji/ee/lib/ee/bulk_imports/groups/graphql/get_epics_query.rb#L45-49 because there can be way over 100 emojis per 1 epic (seen ~300 emojis on 1 epic), which would mean handling of nested paginations.
Instead, create a separate pipeline EpicAwardEmojiPipeline that imports emojis for each individual epic.
Mentions #297466 (closed)
Screenshots (strongly suggested)
| Source | Destination |
|---|---|
 |
 |
To test
- Create group, epic and add emojis to the created epic
- Open rails console
user = User.first
credentials = { url: 'http://gdk.test:3000', access_token: ENV['GITLAB_LOCAL_TOKEN'] }
params = [{ source_type: 'group_entity', source_name: '<name of group you just created>', source_full_path: '<full path of group you just created>', destination_name: "destination", destination_namespace: 'root' }]
BulkImportService.new(user, params, credentials).execute- Alternatively a group can be imported via UI at
/groups/newpage and selecting 'Import group' tab. - Verify newly imported group, it's epic and the award emoji associated with it.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team