# Feature JIM-318 - Introduce status categories

Project: Stream Jira to OpenProject data Migrator
Status: merged
URL: https://community.openproject.org/work_packages/JIM-318

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 18.11.-24.11.2026 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator  
**I want to** be able to choose one of three categories for a status: **To-do**, **In progress**, **Closed**

**Acceptance criteria**

  - There is a status category selector on status creation/update form. Dropdown or radio button.

  - Jira Migrator respects status categories and sets status to appropriate status category.

**Technical notes**

  - **Closed** statuses stay the same.

  - **Not closed** are set to undefined. And it is up to system admin to set it up. Migration:
    
      - Release note asking systems admins to set it up
    
      - Actionable system message asking to set undefined status categories
        
          - <mention class="mention" data-id="80077" data-type="work_package" data-text="###OP-20213" data-display-id="OP-20213">\#\#\#OP-20213</mention>

**Permissions and visibility considerations**

  - Admins

**Translation considerations**

  - Status categories must be translated

**Open Project possible use cases**

  - Additional filters in work package default filters list: **To-do, In progress.**
    
      - No need to enter all in progress statuses one by one.

  - Suggested time tracking entries based on status transitions during the day.
    
      - wp enters an **In progress** status --- time spent in this status --- wp enters not **In progress** status

  - Use status category as a meta status to configure Board columns.

  - Provide SLA reports.
    
      - How much time wp stays in certain status categories?
    
      - It could be an additinal filter similar to statusCategory changed Date JQL function

  - It helps to calculate cycle time metrics.
    
      - From first In Progress status to Closed status in workflow.

**Jira use cases**

  -  Use Case 1: Agile Board Column Display

  - Use Case 2: JQL Filtering with statusCategory

  - Use Case 3: Velocity Chart Calculation

  - Use Case 4: Burndown Chart Calculation

  - Use Case 5: Sprint Completion Logic

  - Use Case 6: statusCategoryChangedDate JQL Function // CLOUD only
    
      - \-- Issues that became Done in last 7 days  
         statusCategory = Done AND statusCategoryChangedDate \>= -7d
    
      - \-- Issues stuck in progress for over 14 days  
         statusCategory = "In Progress" AND statusCategoryChangedDate \<= -14d

  - Use Case 7: Jira Service Management SLA Clock Control

  - Use Case 8: REST API Status Categories Endpoint

  - Use Case 9: Workflow Conditions Based on Category

  - Use Case 10: Resolution Field Auto-Population

  - Use Case 11: Automation Rules Using Status Category

  - Use Case 12: Issue Navigator Color Coding

**Out of scope**

  - 
    <br>
