# Feature OP-15300 - [Work-Packages] Defining work-package-substatuses project-wise

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-15300

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List | UX/UI |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_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

## Situation

As an engineer company, we have different disciplines at work which require different workflows for their work: e.g. in specification, in testing, etc, for software engineering and "in construction", "in drawing", "in procurement", "in assembly" for assembly groups.

Those workflow can have parts in common but some parts differ vastly and confuse people a lot. Additionally, long dropdown lists cannot be used efficiently.

We currently reduce the number of statuses to some core items: "New", "In Progress", "Waiting", "Closed", "Rejected" or even less "Open", "Closed", "Waiting". If it's necessary for a specific product/project/team, to substatus these main statuses, they could potentially optimize their internal worklflows without cluttering the general configuration and also reduce training times for the whole company.

## User Story

**As** a project manager  
**I want to** define substatuses for specific statuses  
**so that** for a specific project I can define a domain-specific workflows

**Acceptance criteria**

  - a user can identifiy the main status of a work-packages (e.g. in progress)

  - the project admin can define substatuses

  - Bonus1: substatuses are made available for other projects, so that project managers can share them across projects without the intervention of an administrator of OpenProject

  - Bonus2: status transitions (workflows) can be defined (but it's a rarely used feature)
