Content
View differences
Updated by Robin Wagner about 10 years ago
**Preconditions**
- Work package module activated.
- Several types exist with different workflows (e.g. bug / task).
**Steps to reproduce**
1. Open work package (e.g. bug).
2. Change status to value which is not allowed by other task (e.g. “in development” -\> not allowed for tasks).
3. Update the type to task (error).
4. Try to change status.
**Actual behavior**
- Status cannot be changed and user has no idea why.
- Type needs to be changed back / to a valid type.
**Expected behavior**
- When type is changed to a type for which the status is invalid, the status is put into edit mode as well and set to the default status.
- Therefore, when saving the status transition, the status is set to the default status while the user still has the chance to cancel the type change.
**Screenshot**
**QA system**
- qa.openproject-edge.com
- dev
- Work package module activated.
- Several types exist with different workflows (e.g. bug / task).
**Steps to reproduce**
1. Open work package (e.g. bug).
2. Change status to value which is not allowed by other task (e.g. “in development” -\> not allowed for tasks).
3. Update the type to task (error).
4. Try to change status.
**Actual behavior**
- Status cannot be changed and user has no idea why.
- Type needs to be changed back / to a valid type.
**Expected behavior**
- When type is changed to a type for which the status is invalid, the status is put into edit mode as well and set to the default status.
- Therefore, when saving the status transition, the status is set to the default status while the user still has the chance to cancel the type change.
**Screenshot**
**QA system**
- qa.openproject-edge.com
- dev