# Feature OP-9531 - [UX] Allow default status per type

Project: OpenProject
Status: rejected
URL: https://community.openproject.org/work_packages/OP-9531

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 7 |
| 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 |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee | Sven Kunze |
| 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

### **Environment**:

Your OpenProject Version: 11.4

Operating System / Browser / OpenProject language: Win/Edge/German

### **Steps to reproduce:**

1.  Define new WP-Type X
2.  Change Workflow of X so that "New" is not available anymore
3.  Create new WP with type X

### **Actual Behavior**

Status "New" is chosen and cannot be changed to something else.

### **Expected Behavior**

  - Allow a default status for each type
  - This status should be choosable in the type's settings, see below (not well drawn but I hope it illustrates the purpose):

<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/23937/content"></div></figure>

### Remark

It's not really a functional issue but a communication and/or usability issue towards the users. Sometimes a different name convey a different meaning which hugely helps users to understand the intent.

Usability: so with a distinct "starting" status, (unexperienced) users don't need to adjust the status to reach the intented one.

Communication: the right starting status signals the intent of the work-package better.
