Reorder epics in an epic

added GitLab Ultimate Plan [DEPRECATED] direction ~2779806 epics labels

added to epic &312 (closed)

changed title from Reorder epics and issues in an epic to Reorder epics in an epic

changed the description

mentioned in issue #7326 (closed)

changed milestone to %11.8

added [deprecated] Accepting merge requests label

added backend label

added frontend label

changed weight to 3

changed the description

added Deliverable label

assigned to @rajatgitlab

removed [deprecated] Accepting merge requests label

mentioned in issue #9121 (moved)

mentioned in issue #9367 (closed)

changed epic to &758 (closed)

assigned to @engwan

I'll work on backend for this. API will also be done here since it can't be added in !9188 (merged) since backend support isn't available yet.

mentioned in merge request !9283 (merged)

created merge request !9283 (merged) to address this issue

added workflowin dev label

Thank you, @engwan. Will pick up the Frontend work once your MR is in master.

@rajatgitlab Do you prefer doing the frontend work in the same MR or in a separate one?

I've done the backend work in !9283 (merged) and I'll have it for review now.

For the frontend, it looks like not much needs to be changed since we're using the same component that's used for reordering issues.

I made this change locally and the ordering works in the UI. We'll have to add tests for this though, so let me know how you prefer to work on this.

diff --git a/ee/app/assets/javascripts/related_issues/components/related_issues_block.vue b/ee/app/assets/javascripts/related_issues/components/related_issues_block.vue
index 2e9426a25e2..5b3a7fbba11 100644
--- a/ee/app/assets/javascripts/related_issues/components/related_issues_block.vue
+++ b/ee/app/assets/javascripts/related_issues/components/related_issues_block.vue
@@ -124,8 +124,8 @@ export default {
       const nextItemEl = itemEl.nextElementSibling;

       return {
-        beforeId: prevItemEl && parseInt(prevItemEl.dataset.epicIssueId, 0),
-        afterId: nextItemEl && parseInt(nextItemEl.dataset.epicIssueId, 0),
+        beforeId: prevItemEl && parseInt(prevItemEl.dataset.orderingId, 0),
+        afterId: nextItemEl && parseInt(nextItemEl.dataset.orderingId, 0),
       };
     },
     reordered(event) {
@@ -231,7 +231,7 @@ export default {
               'card-slim': canReorder,
             }"
             :data-key="issue.id"
-            :data-epic-issue-id="issue.epic_issue_id"
+            :data-ordering-id="issue.epic_issue_id || issue.id"
             class="js-related-issues-token-list-item list-item pt-0 pb-0"
           >
             <issue-item

removed workflowin dev label

added workflowin review label

@engwan Thank you! You simplified the FE work so much. Kudos for that.

I can create an MR against your branch since yours is already under review. Then from there we can either merge my changes to your branch or into master if your changes are merged. Sounds good?