Content
View differences
Updated by Klaus Zanders about 1 month ago
**As** a Resource Manager \[enter role of user\]
**I want to** store resource allocations / allocation requests \[enter objective\]
**so that** I can do proper resource management \[enter desired result\]
**Acceptance criteria**
* A `ResourceAllocation` (RA) model exists.
* The RA is _polymorphically linked_ to an entity (usually a WorkPackage, but maybe later also a project phase, etc)
* The RA is linked to a user or contains a user query, one of them must be filled.
* Nullable `user_id` field
* `user_query` JSON field containing a filter name that is displayed an filter criteria
* A RA has a `state` that will allow resource allocations to be in a certain state (requested, allocated, canceled, etc)
* A RA has start and end dates so we know in which timeframe the resource is allocated and we can have cross checks with the start and end times of the work package
* A RA has allocated work hours. Those should probably be stored in minutes to reduce rounding errors <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** store resource allocations / allocation requests
**so that** I can do proper resource management
**Acceptance criteria**
* A `ResourceAllocation` (RA) model exists.
* The RA is _polymorphically linked_ to an entity (usually a WorkPackage, but maybe later also a project phase, etc)
* The RA is linked to a user or contains a user query, one of them must be filled.
* Nullable `user_id` field
* `user_query` JSON field containing a filter name that is displayed an filter criteria
* A RA has a `state` that will allow resource allocations to be in a certain state (requested, allocated, canceled, etc)
* A RA has start and end dates so we know in which timeframe the resource is allocated and we can have cross checks with the start and end times of the work package
* A RA has allocated work hours. Those should probably be stored in minutes to reduce rounding errors
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._