Content
View differences
Updated by Klaus Zanders 17 days ago
**As** a project manager
**I want to** request the resources
**so that** I can do proper resource management
**Acceptance criteria**
* When allocating a resource, first it is asked if you want to request a specific user or a query:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921571/content">
* Requesting an explicit user requires to select a user using an autocompleter, work package, start and end times (maybe pre selected from the work package time), and how many hours should be allocated:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921590/content">
* Requesting filter criteria looks almost the same, but instead of the user autocompleter we have a user query filter builder and we give that filter a description (i.e. Fullstack-Dev \[de,en\]) and select filter criteria. The screenshot is currently missing how the rest of the form will be handled, but we will define this.<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921591/content">
* When the user is already overallocated, we show a warning dialog.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921592/content">
* When the work package start&end dates do not match up wit the resource allocation, we also show a warning
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921593/content">
**Technical notes**
* As displaying the resource allocations is not yet implemented, after creating one, the result has to be checked in the database <br>
**Permissions and visibility considerations**
* _New permission:_ **Allocate user resources**, per project. Allows you to create a resource allocation for all project's members or a filter. Resource Allocations with those permission are bypassing (the not yet implemented) approval process. The approval process will get its own permissions
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Allocating real users to requested filters (<mention class="mention" data-id="75536" data-type="work_package" data-text="##OP-19444" data-display-id="OP-19444">##OP-19444</mention>)
* Approval process (<mention class="mention" data-id="75538" data-type="work_package" data-text="##OP-19446" data-display-id="OP-19446">##OP-19446</mention>)
* Warning that a user will be overbooked (<mention class="mention" data-id="75780" data-type="work_package" data-text="##OP-19481" data-display-id="OP-19481">##OP-19481</mention>)
* Displaying the allocation progressbar and allocated users (<mention class="mention" data-id="75781" data-type="work_package" data-text="##OP-19482" data-display-id="OP-19482">##OP-19482</mention>)
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** request the resources
**so that** I can do proper resource management
**Acceptance criteria**
* When allocating a resource, first it is asked if you want to request a specific user or a query:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921571/content">
* Requesting an explicit user requires to select a user using an autocompleter, work package, start and end times (maybe pre selected from the work package time), and how many hours should be allocated:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921590/content">
* Requesting filter criteria looks almost the same, but instead of the user autocompleter we have a user query filter builder and we give that filter a description (i.e. Fullstack-Dev \[de,en\]) and select filter criteria. The screenshot is currently missing how the rest of the form will be handled, but we will define this.<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921591/content">
* When the user is already overallocated, we show a warning dialog.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921592/content">
* When the work package start&end dates do not match up wit the resource allocation, we also show a warning
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/921593/content">
**Technical notes**
* As displaying the resource allocations is not yet implemented, after creating one, the result has to be checked in the database
**Permissions and visibility considerations**
* _New permission:_ **Allocate user resources**, per project. Allows you to create a resource allocation for all project's members or a filter. Resource Allocations with those permission are bypassing (the not yet implemented) approval process. The approval process will get its own permissions
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Allocating real users to requested filters (<mention class="mention" data-id="75536" data-type="work_package" data-text="##OP-19444" data-display-id="OP-19444">##OP-19444</mention>)
* Approval process (<mention class="mention" data-id="75538" data-type="work_package" data-text="##OP-19446" data-display-id="OP-19446">##OP-19446</mention>)
* Warning that a user will be overbooked (<mention class="mention" data-id="75780" data-type="work_package" data-text="##OP-19481" data-display-id="OP-19481">##OP-19481</mention>)
* Displaying the allocation progressbar and allocated users (<mention class="mention" data-id="75781" data-type="work_package" data-text="##OP-19482" data-display-id="OP-19482">##OP-19482</mention>)
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._