# Feature RESMA-67 - Create global resource planners

Project: Stream Resource Management
Status: tested
URL: https://community.openproject.org/work_packages/RESMA-67

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Enterprise / Professional (PRO) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Klaus Zanders |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a resource manager  
**I want to** create resource planners outside individual projects  
**so that** I can plan and review resources across multiple projects

**Acceptance criteria**

*   Resource planners can be created in a global, project-independent area.
    
*   A global resource planner can include users, placeholder users and allocations from multiple projects.
    
*   The planner provides the existing resource-planning views and time-period selection.
    
*   Resources and allocations can be filtered by project and other available attributes.
    
*   Existing project-specific resource planners remain available.
    

**Technical notes**

*   Reuse the existing Resource Planner functionality with a global rather than project-specific scope.
    

**Permissions and visibility considerations**

*   Creating and managing global planners requires an appropriate global permission.
    
*   Users only see projects, resources and allocations they are permitted to view.
    
*   We need to define how allocations are shown for invisible work packages and projects, as those are still relevant.
    

**Translation considerations**

**Out of scope**

*   What-if scenarios and alternative plan versions.
    
*   Portfolio prioritization.
    
*   Changing permissions of the included projects.
    

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