# Epic RESMA-1 - Resource management module Project: Stream Resource Management Status: closed URL: https://community.openproject.org/work_packages/RESMA-1 ## Detailed specification ### Motivation and background information ### Acceptance criteria ### Out of scope | Attribute | Value | | --- | --- | | Mockups | https://www.figma.com/design/Xh5P813nnu1HDbVcSkCT3O/Resource-Management?node-id=224-3559&p=f&t=Ix1NHAWFE8WrB7Ql-0 | ## Planning | Attribute | Value | | --- | --- | | Roadmap | 2026 Q3 | | Date | | | Votes | 187 | | List | RM Resource management, RM PPM | | Target versions | | | Relevance | | ## Subitems | ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | RESMA-10 | Feature | Allow nesting Groups | closed | | 17.3.0 | Stream Resource Management | Medium | | | RESMA-13 | Implementation | Implement Resource Planner Meta Resource | closed | | 17.5.0 | Stream Resource Management | Medium | | | RESMA-22 | Feature | Allow Custom Fields on UserQuery | closed | | 17.5.0 | Stream Resource Management | Medium | | | RESMA-23 | Feature | Primerize users administration to allow all filters | closed | | 17.5.0 | Stream Resource Management | Medium | | | RESMA-2 | Feature | Track working hours and availabilities for each user in the system | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-3 | Feature | New Administration for User Custom Fields and Custom Field Sections | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-4 | Feature | Add Departments and Organizational Management to depict the Org Chart | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-11 | Feature | Extend LDAP Sync to build org structure | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-18 | Feature | Build User Card View for Resource Management | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-33 | Feature | Add a field to the user profile that can be used to set the department | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-40 | Feature | Remove feature flag for resource management | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-41 | Feature | Extend demo seeds with departments, more users, working schedule | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-42 | Feature | Special roles for User Attributes | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-47 | Feature | Restrict to premium enterprise plans | closed | | 17.7.0 | Stream Resource Management | Medium | | | RESMA-16 | Feature | Build Workpackage Timeline View for Resource Management | closed | | Product Backlog | Stream Resource Management | High | | | RESMA-17 | Feature | Build User Timeline View for Resource Management | closed | | Product Backlog | Stream Resource Management | High | | | RESMA-14 | Feature | Implement Resource Allocation Resource | closed | | | Stream Resource Management | Medium | | | RESMA-15 | Feature | Allow persisting user queries | closed | | | Stream Resource Management | Medium | | | RESMA-19 | Feature | Build Workpackage List View for Resource Management | closed | | | Stream Resource Management | Medium | | | RESMA-20 | Feature | Implement dialogs to request/create resource allocations | closed | | | Stream Resource Management | Medium | | | RESMA-21 | Open Point | How do we cut enterprise features here? | decided | | | Stream Resource Management | Medium | | | RESMA-26 | Feature | Implement process to allocate real users to generic requests | closed | | | Stream Resource Management | Medium | | | RESMA-30 | Feature | Add Algorithm to distribute a users work over the workweek | closed | | | Stream Resource Management | Medium | | | RESMA-31 | Feature | Modal to display allocated ressources per work package | closed | | | Stream Resource Management | Medium | | | RESMA-38 | Feature | Allow editing details of a resource planner | closed | | | Stream Resource Management | Medium | | ## Bugs and other work packages | ID | Type | Subject | Status | Assignee | Target versions | Module | | --- | --- | --- | --- | --- | --- | --- | | RESMA-48 | Bug | Collection for small bug tickets discovered during QA | closed | Klaus Zanders | 17.7.0 | | | RESMA-53 | Bug | Bubble with + in timeline view does not make sense | closed | | 17.7.2 | Modules and project features / Resource management | | RESMA-58 | Bug | List of filters for creating a work package resource planner have a lot of irrelevant filters | closed | | 17.8.0 | Modules and project features / Resource management | | RESMA-57 | Bug | When creating a Resource Planner with a WorkPackage filter, the Assignee field does not show user names | closed | | 17.8.0 | Modules and project features / Resource management | | RESMA-54 | Bug | Long WP name or timespan doesn't wrap in planner cell | closed | | 17.8.0 | Modules and project features / Resource management, Frontend components and Primer design system | | RESMA-44 | Code maintenance | Clean up duplication in the resource management module | closed | | | | | RESMA-43 | Bug | Can select work packages/users that are not part of the resource planner | closed | | | | | RESMA-21 | Open Point | How do we cut enterprise features here? | decided | | | | ## Details | Attribute | Value | | --- | --- | | Module | | | Enterprise plan | Enterprise / Premium (PRE) | | Labels | | ## People | Attribute | Value | | --- | --- | | Assignee | OP Dev Sirius Team | | Accountable | | | Product manager | | | Designer | Marc Alcobé | | Developers | OP Dev Sirius Team | | Requested by | | | Interest by | Home (224196000003952096) | ## Estimates and progress | Attribute | Value | | --- | --- | | Work | 160d 0h · Σ 250d 0h | ## Description **Use cases** * Do we have the capacity to start another project? * A project member leaves the organization. What does this mean for the project portfolio? * When is a person available for the next project? * The management wants to prioritize a project. What does this mean for the project portfolio? * Do we need to hire additional staff? * We have a delay in one subproject. What does this mean for the other teams?