Content
View differences
Updated by Sven Kunze almost 3 years ago
### **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.
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.