### Feedback:

Begin of the insertion<br>

Jobs and Skills should be managed globally

* Current mockups show both as free-text. They should be manageable by administrators to guarantee that they are consistent all over the organization


End of the insertion _Capacity planning is based on different layers and presupposes the ability to define and manage weekly working capacity per user_

* **Generic resources** similar to op’s placeholder users to visualize needed experts or non-human resources while planning

* Begin of the insertionGeneric resources should have the same attributes (job role, key skills) as regular users to allow for matching

* End of the insertion When it comes to non-human resources, it is essential to to have numerical limitations of every resource that can be assigned, analog to personal users.

* **Group resources** which are based on grouped users and their merged working capacity, to identify available capacity before assigning
Ideally based on user groups so that LDAP group synchronisation can be utilised

* **User resources** which are based on its individual working capacity per week, lineary or dynamically distributed over days.

* Recurring tasks can build a „background noise“, project works cover the remaining capacity

* Unfavourable: Low or excessive utilisation

* Ideal: Medium to high utilisation Begin of the insertion


End of the insertion Begin of the deletion



End of the deletion Scenario Planning (&quot;Draft Mode&quot; / &quot;What-if&quot; Mode):

* Introduction of a &quot;Draft Mode&quot; for resource planning to conduct simulations (e.g., planning scenarios without direct impact on ongoing projects) without real impact on productive data before role based approval Begin of the insertion

* The requirement for this what-if mode is not only limited to resource planning. It also includes project management in general. This is more of a nice-to-have, not a for-now requirement.


End of the insertion Begin of the deletion



End of the deletion Visualization of Utilization:

* Visualization of utilization data, staggered by projects, based on current data or in case of &quot;What if&quot; scenarios (see above) Begin of the insertion


End of the insertion Begin of the deletion



End of the deletion Resource requests vs. assignments

* Distinction between requested and assigned resources (e.g., use of placeholder users in resource management).

* Begin of the insertionThere should be two different ways to assign resources to work packages:

* The project manager requests a specific user. This request is forwarded to the user&#39;s manager (manager isEnd of the insertion Begin of the deletion ClearlyEnd of the deletion defined Begin of the insertioneither as the departments manager or thereEnd of the insertion Begin of the deletion process: One personEnd of the deletion is Begin of the insertiona direct relation on the user that specifies who the user&#39;s manager is. If they approve, the user becomes the assigneeEnd of the insertion Begin of the deletion responsibleEnd of the deletion for Begin of the deletion approving requests, another makesEnd of the deletion the Begin of the insertionwork package.

* The project manager requests a generic role/key skill. They use this for planning and when they &quot;finish&quot; theEnd of the insertion request, Begin of the insertionthe line managers see this request and can assign a specific userEnd of the insertion Begin of the deletion it could be helpfulEnd of the deletion to Begin of the insertionthe request and that person becomes the assignee of the work package.

* So we need to buildEnd of the insertion Begin of the deletion map these information via LDAPEnd of the deletion in Begin of the insertionthis request and approval process. Might not be part of the first iteration, but we should have it in place.


End of the insertion Begin of the deletion bigger organisations



End of the deletion Resources on Parent Work Packages:

* Resource allocation on parent work packages (not just at the lowest level) Begin of the insertion


End of the insertion Begin of the deletion



End of the deletion Daily Business and Availability Factor:

* Begin of the insertionWhen we manage the working timesEnd of the insertion Begin of the deletion SolutionEnd of the deletion for Begin of the insertioneach user, there should beEnd of the insertion Begin of the deletion resources in daily business: Introduction ofEnd of the deletion an availability factor Begin of the insertionthat defines how much time they can be booked on projects. So if a user has a 40hr work week, and a capacity factor of 80%, they are only available for 32hr of project work.

* Availability times should be tracked per working day (scenarios like 37.5hr week where every day is 8hr, except friday which is 5.5hr)

* Availability times should be editable via the API and it should be possibleEnd of the insertion to Begin of the insertionblock editing them in OpenProject itself.End of the insertion Begin of the deletion map capacities.End of the deletion

* Short-term absences (vacation, sickness): Clarification on how to adjust existing project plans. Begin of the insertion

* We need to track those unavailable days per user. At a later stage, we should also see how/if we might need to adjust or warn if that interferes with a project plan.


End of the insertion Begin of the deletion



End of the deletion Extending baseline Begin of the insertioncomparison on work packages:End of the insertion Begin of the deletion comparison:End of the deletion

* Begin of the insertionThe customer asked if there are any plans to have multiple dates selected so that they can better doEnd of the insertion Begin of the deletion Multiple data points forEnd of the deletion comparisons Begin of the insertionover time (i.e. see in one view what changed from one milestone to the other). A workaround is to save queries with baseline enabled so you can quickly switch from one view to the other.

* This is unrelated to resource management.


More granularEnd of the insertion Begin of the deletion



End of the deletion Write Access for Custom Begin of the insertionFields:End of the insertion Begin of the deletion Fields especially in case of estimated work:End of the deletion

* Restrict write access for custom fields, but make them available for specific roles. Begin of the insertion

* They also asked for a special permission to allow editing work/remaining work as they only want to offer this to project managers. This requires <mention class="mention" data-id="22800" data-type="work_package" data-text="#22800">#22800</mention>, so normal project workers can &quot;edit&quot; remaining work by logging time.

* Also something unrelated to Resource ManagementEnd of the insertion


<br>

Context of user:

* [ ] Non-user
* [ ] Uses Community Edition
* [x] Tests OpenProject Enterprise
* [ ] Existing customer
* [ ] Enterprise Cloud
* [x] Enterprise on-prem
* [ ] BIM Cloud
* [ ] BIM on-prem

**Link to Odoo (if applicable)**

* [https://helpdesk.openproject.org/web#id=29765&amp;menu\_id=200&amp;cids=1&amp;action=300&amp;model=crm.lead&amp;view\_type=form](https://helpdesk.openproject.org/web#id=29765&menu_id=200&cids=1&action=300&model=crm.lead&view_type=form)