**As** a Begin of the insertionresource managerEnd of the insertion Begin of the deletion \[enter role of user\]End of the deletion
**I want to** Begin of the insertiongo through all visible allocations that have user attributes and no user assigned yet (i.e. "Developer (EN-DE)") and assign real users to themEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionreal users can do the work.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

**Acceptance criteria**

* Begin of the insertionA new _Staffing_ menu item under _Resource Planning_ that shows a list of all `Resource Allocations` in the project that do not have a user assignment for users that have the permission

* The view that list all of those allocations

* A warning when an allocation starts in the past and is still unassigned

* Alloctions should be sorted by Start time. It should show

* The given filter name (i.e. "_Ruby Developer (EN-DE)_")

* If visible, the work package details

* The start & end dates of the allocation

* The requested amount of time

* Click opens a modal that lists all _project members_ that match the given criteria and show with an indicator if the allocation fits into the user's other allocations or not (same logic that shows a user as overbooked in other places of the codebase)

* A user can be selected from the list and an assign button assigns the user to the resource allocation.End of the insertion Begin of the deletion <br>End of the deletion


**Technical notes**

* Begin of the insertionWhen a user is assigned to the allocation, we **do keep** the `filters` and `filter_name` on the Resource Allocation. It must **not** be removed. `principal_explicit` should also stay `false`.&nbsp;

* Let&#39;s add a new column `principal_assigned_by` on the `ResourceAllocation` model that stores the information who has made the assignment

* When a user is initially selected in the creation of the allocation, this is set to the same user as the \`requested\_by\_id\` 


End of the insertion Begin of the deletion <br>


End of the deletion **Permissions and visibility considerations**

* Begin of the insertionA new `Assign users to generic allocations` permission, givable on the project level.End of the insertion Begin of the deletion _To whom is this feature visible?_

* _When is it not visible?_End of the deletion


**Translation considerations**

* Begin of the insertionSuggestions forEnd of the insertion Begin of the deletion _Key terms and phrases inEnd of the deletion the Begin of the insertionname of the process would either be _Staffing_ or _Resource Assignment_. Looking at that we are already thinking about going away from resource as a word, staffing might be more appropriate.End of the insertion Begin of the deletion key languages_&nbsp;End of the deletion


**Out of scope**

* Begin of the insertionA proper integration with departmentsEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._End of the deletion