Content
View differences
Updated by Jonas Heinrich (Finn) almost 12 years ago
**Preconditions**
- S is the default status.
- Member X that has role R in
\- Normal OP-Installation (occured on .org)
\- Given a project P.
- Workflow for with workflows that forbids transition forbid moving (e.g.) from any status “Tested” to status S “New” for Role R and the given type T.
- Workpackage of type T (e.g.) “Bug”
\- Given a WP with another status. the first status
**Reproduction**
\- click Update and select the Status dropdown
1. As user X go to the work package and click Update.
**Actual**
- Status S is
\- the only item in dropdown offers the dropdown and therefore selected.
- second status
\- Saving without changing anything results in an error message “Status no valid transition exists from old to new status for the current user roles”
- The error message is faulty, i.e. it follows
**Expected**
\- the format “field name + error message” but that is dropdown does not correct in offer the second status
**Notes**
\- this case.
- Furthermore, might be limited to the error message in german New status as it has kind if a typo (Nuter instead of Nutzer).
**Expected**
- Maybe the status should not be changeable at all (greyed out).
- The error messages should be correct. special role
- S is the default status.
- Member X that has role R in
\- Normal OP-Installation (occured on .org)
\- Given a
- Workflow for
- Workpackage of type T
\- Given a WP
**Reproduction**
\- click Update and select the Status dropdown
1. As user X go to the work package and click Update.
**Actual**
- Status S is
\-
-
\-
- The error message is faulty, i.e. it follows
**Expected**
\-
**Notes**
\-
- Furthermore,
**Expected**
- Maybe the status should not be changeable at all (greyed out).
- The error messages should be correct.