# Feature OP-17506 - Improve budget handling in project queries and budget planning

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-17506

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 16.4.0 |
| Sprint | 16.4.0 |
| Backlog bucket |  |
| Votes |  |
| List | PM² PMflex |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| OP-17810 | PDF/XLS export of new budget columns in project list export | Feature | closed |  | 16.4.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-17802 | Bug | New Budget columns leak information to users without view budgets permission | closed |  | 16.4.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Klaus Zanders, Oliver Günther, Christophe Bliard, Mir Bhatia |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

As a project manager, program manager and portfolio manager

I want better budget planning

**Acceptance criteria**

  - We allow to set a fixed amount on a budget without planning material and labor costs. This allows for an easier allocation of money. For example on the top-level budget we do not plan explicit labor, but instead we just assign a lump sum of money.

  - ~~We can define relations between a project's budget with other budgets from the project hierarchy.~~
    
      - ~~Top-down approach: The parent budget has money in it and money is taken out of that parent's budget and allocated into the child budget.~~  
        *~~This can be used when we know the budget for the entire project hierarchy in advance and want to distribute money to its sub-projects.~~*
    
      - ~~Bottom-up approach: The parent does not have any money allocated to itself. Instead the money that is "in" the parent budget is the calculated sum of the children's planned budgets.~~   
        *~~This can be used when we know the budgets for each individual sub-project but do not know the overall budget.~~*
    
      - ~~Those approaches can also be combined. (~~*~~TBD: Add a screenshot that visualizes this~~*~~)~~

  - In the project lists there are additional columns:
    
      - `Budget planned`
    
      - `Budget Spent`
    
      - `Budget Spent (Percentage)`
    
      - `Budget available`

**Out of scope**

  - New permissions

  - Sub totals in the project lists