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

* This applies to kanban-style boards only, so sprint boards and kanban boards created from scratch. 

* Boards display work packages according to column groupings rather than a one-to-one status mapping.

* A board configuration panel shows all columns with their currently mapped statuses. This should be a per-board setting.

* For sprint boards: this should be a permanent setting for all sprint boards, so that users dont have to set it up for each sprint separately.

* We will have a challenge for projects with multiple active sprints, because we cannot identify which board belongs to which sprint/team. For now I would suggest to have only a single setup for sprint boards, no matter if there are MAS active or not. This might be tackled in further iterations (together with the similar challenge on velocity charts).

* Certain edit rights would be needed for a user in order to configure a board. Begin of the insertionSince people can create multiple kanbanEnd of the insertion Begin of the deletion TBD with the team: project admin, separateEnd of the deletion board Begin of the insertioninEnd of the insertion Begin of the deletion admin rights? I haveEnd of the deletion a Begin of the deletion tendency forEnd of the deletion project Begin of the insertioneach user should be able to configure their own boards, so logically as soon as a user can create kanban boards they should be able to edit the status mapping.

End of the insertion Begin of the deletion admin rights.

End of the deletion * Begin of the insertionOpen question: do we want to use different privileges for status mapping within sprint boards? Can we use any existing privileges?

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

* Unmapped statuses are displayed in a dedicated pool/list

* Admins can drag statuses from the pool into any column and between the columns

* 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

* Begin of the insertion~~DefineEnd of the insertion Begin of the deletion DefineEnd of the deletion a default transition status per column, applied when a card is dragged Begin of the insertionin~~End of the insertion Begin of the deletion inEnd of the deletion

* Begin of the insertion~~AsEnd of the insertion Begin of the deletion AsEnd of the deletion 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 Begin of the insertionconsistent.~~End of the insertion Begin of the deletion consistent.End of the deletion

* Begin of the insertion~~EachEnd of the insertion Begin of the deletion EachEnd of the deletion column with multiple mapped statuses has a "default transition status" Begin of the insertionselector~~End of the insertion Begin of the deletion selectorEnd of the deletion

* Begin of the insertion~~TheEnd of the insertion Begin of the deletion TheEnd of the deletion default status must be one of the statuses already mapped to that Begin of the insertioncolumn~~End of the insertion Begin of the deletion columnEnd of the deletion

* Begin of the insertion~~IfEnd of the insertion Begin of the deletion IfEnd of the deletion only one status is mapped, it is automatically the Begin of the insertiondefault~~End of the insertion Begin of the deletion defaultEnd of the deletion

* Begin of the insertion~~WhenEnd of the insertion Begin of the deletion WhenEnd of the deletion a work package is dragged into the column, it transitions to the default status (subject to workflow Begin of the insertionrules)~~End of the insertion Begin of the deletion rules)End of the deletion

* Begin of the insertion~~TheEnd of the insertion Begin of the deletion TheEnd of the deletion default transition status is visible in the column header in the board Begin of the insertionview~~End of the insertion Begin of the deletion viewEnd of the deletion

* 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 unmapped statuses do 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 Begin of the insertion

* Allow multiple drop zones for multiple statuses mappedEnd of the insertion to Begin of the insertiona single column.

* End of the insertion the Begin of the insertionorder of drop zones should reflect the order within the admin mapping area.

End of the insertion Begin of the deletion column's default status

End of the deletion * \[open points\]:

* Begin of the insertion~~WhatEnd of the insertion Begin of the deletion WhatEnd of the deletion if the work package type does not support a certain default Begin of the insertionstatus?~~End of the insertion Begin of the deletion status?End of the deletion

* Begin of the insertion~~IfEnd of the insertion Begin of the deletion IfEnd of the deletion only one of mapped statuses applies to this work package type, automatically select this Begin of the insertionstatus.~~End of the insertion Begin of the deletion status.End of the deletion

* Begin of the insertion~~WhatEnd of the insertion Begin of the deletion WhatEnd of the deletion if it supports multiple statuses mapped, but not the default Begin of the insertionstatus?~~End of the insertion Begin of the deletion status?End of the deletion

* Begin of the insertion~~ShowEnd of the insertion Begin of the deletion ShowEnd of the deletion a modal allowing a user to select the status manually. Begin of the insertion(TBD)~~End of the insertion Begin of the deletion (TBD)End of the deletion

* 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.

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