* Users can group multiple workflow statuses into a single board column.

* Boards display work Begin of the insertionpackagesEnd of the insertion Begin of the deletion itemsEnd of the deletion according to column groupings rather than a one-to-one status mapping.

* Begin of the insertionA board configuration panel shows allEnd of the insertion Begin of the deletion Moving or dragging a work item betweenEnd of the deletion columns Begin of the insertionwith their currently mapped statuses. This should beEnd of the insertion Begin of the deletion results inEnd of the deletion a Begin of the insertionper-board setting.End of the insertion Begin of the deletion predictable and understandable status change.End of the deletion

* Begin of the insertionCertain edit rights would be needed forEnd of the insertion Begin of the deletion Existing boards that rely onEnd of the deletion a Begin of the insertionuser in orderEnd of the insertion Begin of the deletion one-to-one relationship between columns ands statuses continueEnd of the deletion to Begin of the insertionconfigure a board. TBD with the team: project admin, separate board admin rights?

End of the insertion Begin of the deletion work without change.

<br>

End of the deletion * It is clear to Begin of the insertionboardEnd of the insertion users which workflow statuses are represented by each board column. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionUnmapped statuses are displayed in a dedicated pool/list

* Admins can drag statuses from the pool into any column

* Admins can remove a status from a column, returning it to the unmapped pool

* Each status can only be mapped to one column at a time

* Define a default transition status per column, applied when a card is dragged in

* As a board administrator, I want to define which status is applied by default when a work package is dragged into a column, so that transitions are predictable and consistent.

* Each columnEnd of the insertion Begin of the deletion UsersEnd of the deletion with multiple Begin of the insertionmapped statuses has a "default transition status" selector

* The default status must be one of the statuses already mapped to that column

* If only one status is mapped, it is automatically the default

* When a work package is dragged into the column, it transitions to the default status (subject toEnd of the insertion workflow Begin of the insertionrules)

* The default transition status is visible in the column header in the board view

* Configure unmapped status behavior

* As a board administrator, I want to control what happens to work packages whose status is not mapped to any column, so that my board stays clean and relevant.

* Board settings include an "Unmapped status behavior" option with two modes:

* Hide: Work packages with unmappedEnd of the insertion statuses Begin of the insertiondo not appear on the board

* Show in dedicated lane: They appear in a special "Unmapped" column at the end of the board

* The selected behavior is persisted per board configuration

* Drag and drop with status transition

* As a team member, I want to drag a work package to a different column and have its status automatically updated to the column's default transition status, so that I don't have to manually update the status separately.

* Dragging a work package to a column triggers a status transition to the column's default status

* \[open points\]:

* What if the work package type does not support a certain default status?

* If only one of mapped statuses applies to this work package type, automatically select this status.

* What if it supports multiple statuses mapped, but not the default status?

* Show a modal allowing a user to select the status manually. (TBD)

* What if it does not support any of the statuses in a column?

* If the transition is not allowed by the current workflow rules, the drag is rejected with a clear error message and the card snaps back. Preserve workflow integrity: status transitions must still respect existing workflow permission rules.

* We have to also handle cases where certain status transitions are not available to some users (e.g. certain role does not have rights to conduct a specific status transition).

* If the transition is not allowed by the role / privileges, the drag is rejected with a clear error message and the card snaps back. Preserve role integrity.

* Existing boards that rely on a one-to-one relationship between columns and statuses continue to work without change.

* UsersEnd of the insertion can configure boards to display fewer columns ( e.g. "To do", "In progress", "Done") than the number of Begin of the insertionstatuses available in the board.End of the insertion Begin of the deletion statuses.End of the deletion