# Feature OP-19131 - Planned labor costs without selecting a certain user (budgets)

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-19131

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 | Modules and project features / Costs and budgets |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | OP Dev Sirius Team |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a manager of a project budget  
**I want to** add planned labor costs to a budget without selecting a certain user  
**so that** I can set up a budget without knowing all project members and their duties within this project

**Context**:

Often, a project administrator does not know which members of their team will be working on a new project. Team members change, so it is unlikely that this can be foreseen when the project budget is set. While it is not yet clear who will work on a project, it is possible to plan for the labour costs though.

**Acceptance criteria**

*   It is possible to plan labor costs in a budget WITHOUT selecting a certain user
    
*   If a user books time against a work packaged which is connected to a budget, their hourly rate will be applied automatically and calculated against the planned labor costs
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_&nbsp;
    

**Out of scope**

*   <br>
    

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