# Epic AGILE-34 - Status mapping within columns in sprint and kanban boards

Project: Stream agile
Status: in specification
URL: https://community.openproject.org/work_packages/AGILE-34

## Detailed specification

### Motivation and background information

Users migrating from Jira are accustomed to grouping multiple workflow statuses into a single Kanban/Sprint board column. For example, an **“In Progress”** column may include statuses such as **“In Development”** and **“In Code Review.”**

In Jira, columns are distinct from statuses: columns provide a **visual grouping of work**, rather than representing the status itself. When a card is moved into a column, Jira either assigns a default status associated with that column or prompts the user to choose one if multiple statuses are available.

In contrast, OpenProject uses a **one-to-one relationship between columns and statuses**. Each board column directly represents a single workflow status. Dragging a card into a column automatically sets the card’s status to that column’s status, and renaming a column requires changing the underlying workflow.

### Acceptance criteria

*   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.&nbsp;
        
    *   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. Since people can create multiple kanban board in a project each 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.
        
        *   Open question: do we want to use different privileges for status mapping within sprint boards? Can we use any existing privileges?
            
    *   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
        
*   ~~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 column with multiple mapped statuses has a &quot;default transition status&quot; 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 to workflow rules)~~
        
    *   ~~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 &quot;Unmapped status behavior&quot; 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 &quot;Unmapped&quot; 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&#x27;s default transition status, so that I don&#x27;t have to manually update the status separately.
        
    *   Dragging a work package to a column triggers a status transition
        
        *   Allow multiple drop zones for multiple statuses mapped to a single column.
            
            *   the order of drop zones should reflect the order within the admin mapping area.
                
    *   \[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.
    
    *   Users can configure kanban boards to display fewer columns ( e.g. &quot;To do&quot;, &quot;In progress&quot;, &quot;Done&quot;) than the number of statuses available in the board.

### Out of scope

*   Automatic import of board column mappings from Jira during migration
    
*   Automations triggered by column transitions

| Attribute | Value |
| --- | --- |
| Mockups | https://www.figma.com/design/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=4758-90691&t=eIatauiUCjym3vzR-1 |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| Votes |  |
| List | RM Agile |
| Target versions |  |
| Sprint | 3. MLP Scope - New Boards |
| Backlog bucket |  |
| Relevance | Important — Required Short-Term |

## Subitems

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| AGILE-179 | Idea | Spike porting Angular boards to React (with Primer React) | on hold | Alexander Coles |  | Modules and project features / Backlogs, Frontend components and Primer design system |
| AGILE-92 | Idea | Spike building new Agile functionality on existing Boards + Primer React | on hold | Alexander Coles |  | Modules and project features / Backlogs, Frontend components and Primer design system |

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan | Enterprise / Premium (PRE) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Julia Racsko |
| Accountable | Rosanna Sibora |
| Product manager | Rosanna Sibora |
| Feature Lead |  |
| Designer | Julia Racsko |
| Developers | OP Dev Polaris Team |
| Requested by |  |
| Interest by | Black (37919), Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 70d 0h · Σ 70d 0h |

## Description

**As a** user, &nbsp;

**I would like to** group multiple workflow statuses into a single board column

**So that** the board accurately reflects how my team works, looks more compact, and provides some level of flexibility.
