Move promoting issues to UpdateService
What does this MR do?
This is a refactoring to move code responsible from promoting issues from InterpretService
to UpdateService
.
Some of the reasons to do this:
-
Most of other quick actions on interpret service are returning parameters to be applied on update service instead of performing the update.
-
Prevents multiple
/promote
quick actions to be executed creating multiple epics -
There is no way to promote issues on other places, if we decide to do so this now can be easily achieved. Like on API.
PS: I will also create a follow up merge request to prevent issues being promoted when promoted_to_epic_id
is already present. Also we should probably move other quick actions related to epics into their respective UpdateService
.
related to https://gitlab.com/gitlab-org/gitlab/-/issues/208974