| The budget page allows you to enter all expenses and all team positions you expect the folio will require during its lifespan. Expenses are added to one of three main categories: Operational expenditures (OPEX), Capital expenditures (CAPEX) or Financial expenditures (FINEX). The section on categories explains each one in detail. Planned expenses can be single occurence or recurrent ones. Positions are the team members you will need to accomplish the work, such as developers, testers, team leads, etc. and are added to the operational expenditures. Information entered here will be used to provide project health metrics on the Overview page and shown as a reference on the Forecast charts. 
| Anchor |
|---|
| BudgetCategories |
|---|
| BudgetCategories |
|---|
|
CategoriesFolio uses a classic categorization of expenses to better structure your budget. Every expense planned in a budget belongs to one of three main categories: Operational expenditures (OPEX), Capital expenditures (CAPEX) or Financial expenditures (FINEX). Each of these categories will be shown only if it holds at least one expense in it for a given budget. Once a category is displayed on screen, you can collapse it or expand it by clicking on the triangle icon ( ) next to the category name. You should define expenses in their appropriate category so that you can later get relevant information about the categories themselves, like the total cost planned for all capital expenses. Operational expenditures (OPEX) Operational expenditures are all non-capital expenses incurred during normal operation. They are the day-to-day expenses required during the execution of a project, such as the salaries, rent, insurance, electricity, and computer maintenance contracts. They do not include physical assets or loan financing for example. All positions added to a budget are automatically added to the OPEX category. Capital expenditures (CAPEX)Capital expenditures are used by an organization to acquire or upgrade physical assets with a useful life extending beyond the taxable year. Examples of capital expenses are purchase of a computer, photocopier or building. Financial expenditures (FINEX)Financial expenditures are usually interest expenses, such as loan financing, credit card interest, etc. ExpensesExpenses correspond to amounts spent to attain the objectives of the portfolio. They can belong to any of the three categories described in section Categories: OPEX, CAPEX or FINEX. Expenses can be single occurrence, or they can be recurrent. Recurrent expenses can also be amortized; in which case the amount associated with the payment will be evenly split on the payment period. Expenses should represent all money that you plan to be spent during the folio's time frame, such as rents, maintenance contracts, software license purchases, loan financing costs or mortgages. See Budget Expense for more information PositionsPositions are the salary expenses you plan the folio will incur at one point or another. They are operational expenditures. Positions are grouped by title (e.g. Developer, Architect, Q&A). You can collapse (or expand) a group of positions by clicking the triangle icon ( ) next to a position title. Example of positions could be J2EE Developer 1, System Architect, Test Automation Specialist, etc. See Budget Position for more information Scope 
| Details |
|---|
 | Display portfolio scope panel |
|---|
| X | Hide the scope panel |
|---|
| Clicking on information icon will show you online definitions of elements displayed |
|---|
| Saved filter | Clicking on Saved Filter link display the all JIRA issues included in your portfolio |
|---|
| Max. Effort/Person | Indicates the maximum regular hours for a single person within the portfolio's dates. |
|---|
| Planned positions | Indicates the total number of positions currently planned in the budget |
|---|
| Planned Effort | Indicates the total number of hours currently planned in the budget |
|---|
| Breakdown By Issue Type |
|---|
| Issue Type | Issue Type |
|---|
| Count | Total number of issues by type |
|---|
| Earned Value Field | Total number of earned values by issue type Note that this column will not be display if earned value field is "Original Estimate" |
|---|
| Original Estimate | Total original time estimate by issue type |
|---|
|