Content
View differences
Updated by Hagen Schink over 12 years ago
When I migrate a database in which the default status is different to status at the first position, the planning element migration assigns the wrong default status to the new created work packages.
### Precondition
To reproduce the issue we need a database with the following properties:
1. it contains planning elements with no planning element type
2. the default status is not the first status in the status list (see settings)
### Reproduction
1. Migrate a database that contains data mentioned in the preconditions
2. In OpenProject, open the edit dialog of a work package of a former planning element with no planning element type
### Behavior
**Expected:** The status in the edit view is the same as the one displayed in the show view.
**Actual:** The status in the edit view matches the first status in the status list.
### Precondition
To reproduce the issue we need a database with the following properties:
1. it contains planning elements with no planning element type
2. the default status is not the first status in the status list (see settings)
### Reproduction
1. Migrate a database that contains data mentioned in the preconditions
2. In OpenProject, open the edit dialog of a work package of a former planning element with no planning element type
### Behavior
**Expected:** The status in the edit view is the same as the one displayed in the show view.
**Actual:** The status in the edit view matches the first status in the status list.