Content
View differences
Updated by Jens Ulferts about 6 years ago
### Acceptance criteria
* Scheduling mode is persisted in the database
* Scheduling mode is present in the work package resource
* Could be represented by a boolean field or by an enumeration
* Scheduling mode is present in the work package schema
* The scheduling mode can be modified via the API
* Requires no extra permission. Add/Edit work packages suffices.
### Out of scope
* Business logic when scheduling and when activating/deactivating manual/automatic scheduling.
### Implementation notes
* Add a boolean field to the database.
* Add a boolean field to the work package resource.
* Describe the field in the work package schema resource.
* Add the attribute to the contract.
* Add the attribute to the default values within the SetAttributesService (default: automatic scheduling).
* If opportunity arrises: Refactor TypedWorkPackageSchema and SpecifcWorkPackageSchema to be simple Contracts just like it is handle for the rest of the resources.
* Scheduling mode is persisted in the database
* Scheduling mode is present in the work package resource
* Could be represented by a boolean field or by an enumeration
* Scheduling mode is present in the work package schema
* The scheduling mode can be modified via the API
* Requires no extra permission. Add/Edit work packages suffices.
### Out of scope
* Business logic when scheduling and when activating/deactivating manual/automatic scheduling.
### Implementation notes
* Add a boolean field to the database.
* Add a boolean field to the work package resource.
* Describe the field in the work package schema resource.
* Add the attribute to the contract.
* Add the attribute to the default values within the SetAttributesService (default: automatic scheduling).
* If opportunity arrises: Refactor TypedWorkPackageSchema and SpecifcWorkPackageSchema to be simple Contracts just like it is handle for the rest of the resources.