**As** a user of Begin of the insertionOpenProject'sEnd of the insertion Begin of the deletion OpenProject'sEnd of the deletion Backlogs module
**I want to** use drag and drop to move items
**so that** can manage my backlogs, buckets and sprints effectively.

Begin of the insertion---End of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

Begin of the insertion### Acceptance Criteria (Refined)End of the insertion Begin of the deletion _Reorder and move_End of the deletion

Begin of the insertion#### Scenario 1: Reordering within the same list
End of the insertion * Begin of the insertion**Given** aEnd of the insertion Begin of the deletion AEnd of the deletion user with Begin of the insertion"manageEnd of the insertion Begin of the deletion permission to manageEnd of the deletion backlog/sprint Begin of the insertionitems" permissions
* **When** they dragEnd of the insertion Begin of the deletion items can reorderEnd of the deletion a Work Begin of the insertionPackageEnd of the insertion Begin of the deletion packageEnd of the deletion card Begin of the insertionup or downEnd of the insertion within Begin of the deletion a Backlogs list (changingEnd of the deletion its Begin of the insertioncurrent list
* **Then** a visual drop indicator (highlighted gap) appears at valid drop positions.
* **And When** they dropEnd of the insertion Begin of the deletion Position);End of the deletion the Begin of the insertioncard
* **Then** the card instantly moves to theEnd of the insertion new Begin of the insertionposition (optimistic update).
* **And** the newEnd of the insertion order Begin of the insertionis persisted to the server.
End of the insertion Begin of the deletion persists.

End of the deletion * Begin of the insertion**And** refreshing the page confirms the new order.

#### Scenario 2: Moving between lists
* **Given** aEnd of the insertion Begin of the deletion AEnd of the deletion user Begin of the insertionwith "manage backlog/sprint items" permissions
* **When** they dragEnd of the insertion Begin of the deletion can moveEnd of the deletion a Begin of the deletion Work packageEnd of the deletion card Begin of the insertionfromEnd of the insertion Begin of the deletion between Backlogs lists —End of the deletion an Inbox Begin of the insertionbacklog
* **And** hover overEnd of the insertion Begin of the deletion backlog, a Backlog bucket, or a Sprint — including intoEnd of the deletion an empty Begin of the insertionSprint list
* **Then**End of the insertion Begin of the deletion Backlogs list;End of the deletion the Begin of the insertionempty Sprint list visually indicates it can accept the drop.
End of the insertion Begin of the deletion move persists.

End of the deletion * Begin of the insertion**When** theyEnd of the insertion Begin of the deletion During a drag, a Highlighted gapEnd of the deletion drop Begin of the deletion indicator marksEnd of the deletion the Begin of the insertioncard
End of the insertion Begin of the deletion candidate Position, shown as the gap above or below a Work package card.

End of the deletion * Begin of the insertion**Then** theEnd of the insertion Begin of the deletion A scrollable Backlogs list auto-scrolls when aEnd of the deletion card Begin of the insertioninstantly appears in the Sprint list.
End of the insertion Begin of the deletion is dragged near its top or bottom edge.

End of the deletion * Begin of the insertion**And** the moveEnd of the insertion Begin of the deletion Each Backlogs list either accepts dropped Work package cards or does not — dropEnd of the deletion is Begin of the insertionpersisted to the server.

#### Scenario 3: Missing Permissions
End of the insertion Begin of the deletion enabled per list, not filtered per card. _(To confirm: acceptance is all-or-nothing per Backlogs list.)_

End of the deletion * Begin of the insertion**Given** aEnd of the insertion Begin of the deletion AEnd of the deletion user Begin of the insertion**without** "manageEnd of the insertion Begin of the deletion without permission to manageEnd of the deletion backlog/sprint Begin of the insertionitems" permissions
* **When** they attempt to click and drag a Work Package card
* **Then** the cardEnd of the insertion Begin of the deletion itemsEnd of the deletion cannot Begin of the insertionbe picked up (noEnd of the insertion drag Begin of the insertionstate is initiated).End of the insertion Begin of the deletion cards.


_Optimistic behaviour_End of the deletion

Begin of the insertion#### Scenario 4: Optimistic Update Failure (Server Error)
End of the insertion * Begin of the insertion**Given** a user drags and drops aEnd of the insertion Begin of the deletion On drop, the Work packageEnd of the deletion card Begin of the deletion movesEnd of the deletion to Begin of the insertionaEnd of the insertion Begin of the deletion itsEnd of the deletion new Begin of the insertionposition
* **When**End of the insertion Begin of the deletion Position immediately, beforeEnd of the deletion the server Begin of the insertionreturns an error (e.g., network failure or concurrent edit)
End of the insertion Begin of the deletion confirms.

End of the deletion * Begin of the insertion**Then**End of the insertion Begin of the deletion IfEnd of the deletion the Begin of the deletion reorder or move fails, theEnd of the deletion card Begin of the insertionrevertsEnd of the insertion Begin of the deletion returnsEnd of the deletion to its original Begin of the insertionposition.
* **And**End of the insertion Begin of the deletion Position andEnd of the deletion an error Begin of the insertionflashEnd of the insertion notice is Begin of the insertiondisplayed explaining the failure.

#### Scenario 5: Card Visibility After Move
End of the insertion Begin of the deletion shown.

End of the deletion * Begin of the insertion**Given**End of the insertion Begin of the deletion IfEnd of the deletion a Begin of the insertionuser's current view filters out closed items
* **When** they drag a card into a Sprint where a workflow rule automatically closes it
* **Then** the card disappears from the view.
* **And** a notification/toast is shown informing the user that theEnd of the insertion moved Begin of the insertionitemEnd of the insertion Begin of the deletion Work packageEnd of the deletion is no longer visible in the current Begin of the insertionview.End of the insertion Begin of the deletion view after the move, the user is notified.


_Gestures_End of the deletion

Begin of the insertion#### Scenario 6: Auto-scrolling
End of the insertion * Begin of the insertion**Given** a Backlogs listEnd of the insertion Begin of the deletion Drag worksEnd of the deletion with Begin of the insertiona vertical scrollbar
End of the insertion Begin of the deletion mouse and trackpad on desktop.

End of the deletion * Begin of the insertion**When** a user drags a card to the top 10% or bottom 10% of the list container
* **Then** the list automatically scrollsEnd of the insertion Begin of the deletion Touch (mobile / tablet) drag is supported. The touch-initiation gesture and technical approach are trackedEnd of the deletion in Begin of the insertionthat direction.End of the insertion Begin of the deletion #AGILE-293.


_Accessibility (baseline)_End of the deletion

Begin of the insertion#### Scenario 7: Accessibility (Keyboard/Non-Drag Fallback)
End of the insertion * Begin of the insertion**Given** anyEnd of the insertion Begin of the deletion AEnd of the deletion Work Begin of the insertionPackageEnd of the insertion Begin of the deletion packageEnd of the deletion card Begin of the insertion
* **When** a user opensEnd of the insertion Begin of the deletion can be moved without drag, viaEnd of the deletion the Begin of the insertioncard's context menu /End of the insertion move dialog Begin of the insertion
* **Then** they can move itEnd of the insertion Begin of the deletion (to Sprint /End of the deletion to Begin of the insertiona different Sprint orEnd of the insertion Backlog Begin of the insertionBucket without using drag and drop.
End of the insertion Begin of the deletion bucket).

End of the deletion * Begin of the insertion**And**End of the insertion Begin of the deletion Backlogs lists expose `aria-busy`End of the deletion while a Begin of the deletion reorder orEnd of the deletion move is Begin of the insertionprocessing, the target list has the `aria-busy="true"` attribute set.End of the insertion Begin of the deletion being persisted.


**Technical notes**End of the deletion

Begin of the insertion---

### Gap Analysis & Implementation Notes

1. **Drop Rejection Feedback:** If an item cannot be dropped (e.g., restricted type), the drop indicator (gap) must not appear.
2. **Concurrent Modifications:** Handled via Scenario 4 (Revert + Notification).
3. **Visual Source State:** While dragging, the original card should remain in the list with reduced opacity (0.4) to act as a "ghost" placeholder.
4. **Auto-scrolling Threshold:** Defined as the top/bottom 10% of the list's viewport.
5. **Pagination:** Items can only be dropped into currently loaded regions of the list.

### Technical Notes

End of the insertion * Migrating Backlogs DnD from dragula to Atlassian Pragmatic DnD (#AGILE-251). Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Reusable `sortable-lists` Stimulus primitive in `frontend/src/stimulus/controllers/dynamic/`; Backlogs is the first consumer. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Begin of the insertion**Mobile/Touch Support:** Verified that nativeEnd of the insertion Begin of the deletion Controller topology under discussion in #AGILE-292 — recommendation: single root + first-class `list`/`item` leaf controllers via outlets. Not yet a final decision.

* Touch (mobile / tablet) drag is not provided by Pragmatic's element adapter (nativeEnd of the deletion HTML5 Begin of the insertionDnD (Pragmatic's default adapter) does not fire `DragEvents` for finger-touch. This requires either polyfilling or a Pointer Events implementation (trackedEnd of the insertion Begin of the deletion DnD); delivery is trackedEnd of the deletion in Begin of the insertion#AGILE-293).
End of the insertion Begin of the deletion #AGILE-293.

End of the deletion * Begin of the insertionController topology:End of the insertion Begin of the deletion Direction so far:End of the deletion single root per page Begin of the insertion+ leaf controllers for list/item.
End of the insertion Begin of the deletion = whole interaction surface; type-driven drop acceptance (per-list, multi-valued); elements can be both list and item; root holds a `type → move-URL` map; collection move endpoint per type with `ids[]` in the body (single = `[id]`); multi-select state as a root-owned `Set<itemId>`.

End of the deletion * Related: Begin of the insertion#AGILE-175, #AGILE-181, #AGILE-278, #AGILE-284.End of the insertion Begin of the deletion #AGILE-175 (draggable buckets/sprints), #AGILE-181 (multi-select + batch move), #AGILE-278 (bulk move action), #AGILE-284 (optimistic reordering).


**Permissions and visibility considerations**End of the deletion

Begin of the deletion * Reordering and moving require permission to manage backlog/sprint items.


**Translation considerations**

* _Key terms and phrases in the key languages_&nbsp;


End of the deletion **Out of scope** Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Multi-select and batch move (#AGILE-181). Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Reordering whole Backlogs lists, buckets, or sprints (#AGILE-175). Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Long-press and advanced gestures beyond basic touch drag. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Keyboard-operable drag-and-drop and screen-reader drag/drop announcements. Begin of the insertion
End of the insertion Begin of the deletion


<br>End of the deletion