### Description

Retire Dragula from the shared Stimulus drag-and-drop controller by migrating `generic-drag-and-drop.controller.ts` to Begin of the insertionthe `sortable-lists` Stimulus suite built on Atlassian Pragmatic DragEnd of the insertion Begin of the deletion dnd-kit,End of the deletion and Begin of the insertionDrop, andEnd of the insertion make the rollout complete only when all current consumers of that shared controller work and are verified.

Begin of the insertion> **Note:** this work package originally targeted dnd-kit. The library decision has since been made in favour of Pragmatic Drag and Drop (evaluation in #PT-139, decision recorded in #DREAM-672 / #DREAM-674); the description was rewritten accordingly on 2026-07-12.

End of the insertion This is not just a like-for-like port. The target is a clean, idiomatic Begin of the deletion dnd-kit + StimulusEnd of the deletion implementation Begin of the insertionon the shared `sortable-lists` primitives (#AGILE-292)End of the insertion with a stricter shared DOM contract and less controller-side reconciliation. We generally own the markup, so changing component structure, Turbo update boundaries, controller mount points, or small shared ViewComponent/helper abstractions is acceptable where that leads to a simpler design.

**In scope:**

* Begin of the deletion Backlogs

* End of the deletion `Admin::Enumerations::IndexComponent` Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * `Settings::ProjectCustomFieldSections::{Index,Show}Component` Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * `Settings::ProjectPhaseDefinitions::IndexComponent` Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * `WorkPackageTypes::ExportTemplateListComponent` Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Meetings subclass Begin of the insertion

End of the insertion Begin of the deletion


End of the deletion **Out of scope:**

* Begin of the insertionBacklogs — migrated directly to the `sortable-lists` suite under #AGILE-251 / #AGILE-291 (no longer part of this WP).
* End of the insertion Backlogs-specific advanced-surface work such as whole-card drag / drag-handle removal, multi-select / multi-drag, and unifying Begin of the insertion"Move to"End of the insertion Begin of the deletion “Move to”End of the deletion menu actions with the frontend reorder pipeline Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Independent Dragula Stimulus controllers outside the shared controller Begin of the insertion(`reporting/page.controller.ts`, `admin/type-form-configuration/rows-drag-and-drop.controller.ts`, `admin/custom-fields.controller.ts`) — tracked separately under #DREAM-677

End of the insertion Begin of the deletion


End of the deletion ### Acceptance criteria

* Dragula is removed from Begin of the insertion`generic-drag-and-drop.controller.ts` (or the controller is retired outright in favour of `sortable-lists` controllers).
End of the insertion Begin of the deletion `generic-drag-and-drop.controller.ts`.

End of the deletion * All current consumers of the shared controller work on Begin of the insertionthe Pragmatic-based `sortable-lists` suite.
End of the insertion Begin of the deletion dnd-kit.

End of the deletion * The implementation uses Begin of the insertionthe `sortable-lists` primitivesEnd of the insertion Begin of the deletion dnd-kit APIsEnd of the deletion and Stimulus lifecycle where possible, instead of accumulating custom DOM-repair logic. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * `data-target-container-accessor` is treated as a cleanup target; preferred end state is that the controller targets the real sortable container element directly. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Any Begin of the deletion backlog orEnd of the deletion meetings specialization remains on Begin of the insertionthe shared suiteEnd of the insertion Begin of the deletion dnd-kitEnd of the deletion rather than preserving Dragula as an escape hatch. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Same-list reorder responses Begin of the insertionfollow the optimistic contract established in #AGILE-322: an event-only turbo-stream response that carries `WORK_PACKAGE_MOVED_EVENT` (or the surface's equivalent) instead of re-rendering the frame. A bareEnd of the insertion Begin of the deletion may useEnd of the deletion `204 No Content` Begin of the insertionwas explicitly rejected there because it has no body to carryEnd of the insertion Begin of the deletion whereEnd of the deletion the Begin of the insertionevent and breaks listeners such asEnd of the insertion Begin of the deletion optimistic client move already representsEnd of the deletion the Begin of the insertionsplit-view `lock_version` refresh (see https://github.com/opf/openproject/pull/24157).
End of the insertion Begin of the deletion final state.

End of the deletion * Cross-tab/session consistency is treated separately and should come from explicit Turbo Stream broadcasts, not as a side effect of the initiating drag response. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Shared-controller verification covers the full current consumer set, including meetings. Begin of the insertion

End of the insertion Begin of the deletion


End of the deletion ### Begin of the insertionNotesEnd of the insertion Begin of the deletion **Notes**End of the deletion

* Backlogs future work remains separate: Begin of the insertion#73473, #73729
End of the insertion Begin of the deletion

End of the deletion * Begin of the deletion <mention class="mention" data-id="73473" data-type="work_package" data-text="##73473">##73473</mention>

* <mention class="mention" data-id="73729" data-type="work_package" data-text="##73729">##73729</mention>

* End of the deletion This WP may lay groundwork that helps those follow-ups, but their requirements should not bloat the shared controller contract. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Reassess the controller with the assumption that custom reconciliation is guilty until proven necessary. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * In particular, Begin of the insertionre-evaluate against the `sortable-lists` suite as implemented in https://github.com/opf/openproject/pull/23218:
End of the insertion Begin of the deletion re-evaluate:

End of the deletion * Begin of the insertionroot/list/item controller topology and outlet wiring (#AGILE-292)
End of the insertion Begin of the deletion dnd-kit sortable `index` / `initialIndex` / `group` / `initialGroup`

End of the deletion * Begin of the insertiondrop-intent resolution in `drag-and-drop.ts` and the `list-dom.ts` DOM contract
End of the insertion Begin of the deletion `Sortable.target` for nested surfaces

End of the deletion * Begin of the insertion`@atlaskit/pragmatic-drag-and-drop-auto-scroll` configuration
End of the insertion Begin of the deletion `Feedback.configure(...)`

End of the deletion * Begin of the insertionthe Turbo morph guard (`pragmatic-dnd-morph-attributes.ts`)
End of the insertion Begin of the deletion real `AutoScroller` config (`acceleration` / `threshold`)

End of the deletion * Temporary workarounds such as subtree observation should be treated as tactical only and removed before merge if a cleaner markup-driven solution is available.