# Feature OP-15947 - Individual configuration of states and workflows 

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

## Planning

| Attribute | Value |
| --- | --- |
| Date | 2024-10-07 –  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| List |  |
| 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 | Enterprise / Corporate (COR) |

## 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

# Individual configuration of states and workflows

**As** a OP project-admin  
**I want to** configure the states and the workflows of every project individual&nbsp;  
**so that** I can setup projects individual for the customer proccesses and needs.

For example, a small internal project can have a simpler and have a more open configuration than a large customer project.

## Workaround

Create the same state e.g. &quot;in progress&quot; for every project in the admin area. &quot;in progress (customer)&quot; &quot;in progress (company)&quot;

*   bad integration with linked projects (reference, copy a task)
    
*   messy configuraiton
    

## **Acceptance criteria**

*   Add the same configuration in the porject-settings as in the system administration.
    
*   The navigation menu item &quot;Work package types&quot; will be found as a child element &quot;Types&quot; in the group &quot;Work packages&quot;
    
*   The configuration states and workflows are also included in the Group &quot;Work packages&quot;, implemented as in the administration area
    
    <img class="image_resized op-uc-image op-uc-image_inline" style="width:255px;" src="/api/v3/attachments/200060/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/200061/content"><img class="image_resized op-uc-image op-uc-image_inline" style="width:241px;" src="/api/v3/attachments/200062/content">
    
*   If a new project is created the project will copy the default configuration of the administration
    
*   If a new project is created with a other project as a template the project will copy the configuration of the template project
    
*   The configuration in the project overwrites the configuration of the administration with its individual changes, for each status or workflow separately.
    
    *   Therefore if a state is changed to &quot;read-only&quot; in the project-settings, this state is now overwriten by the project.
        
    *   If the state is not changed by the project-settings, you can still change it globally in the admin area.
        
*   if a custom-project state is created, the connection to the original admin state should be stored.
    
    *   the projects should still be integrated nicely e.g. you can copy a task into a other project with a custom state.
        
    
    <br>
