| The Issue Costs Report gives you insight on planned and actual costs and revenues, broken down by the issues that constitute the scope of your a Folio. The report lets you quickly see what issues did cost more than what was planned, and on which ones allowed you to save money was saved. It also lets you allows to filter costs by issue type, helping you, for instance , to determine how much money was spent on bug fixing since the project began. You can obtain a printable version using the report's action menu (...) or by hitting p while consulting it.The issue report can be printed and exported to Excel format. | Info |
|---|
This report is available for Folios only. |
Column definitions| Name | Description |
|---|
| Key | JIRA Issue key | | Summary | Issue summary | | ∑ Effort | Total effort logged by the folio Folio team members that are synchronized with JIRA.Note that effort Effort logged by a team member who is not synchronized with JIRA and by non folio member are discarded
Also note that costs associated to non synchronized folio team members are distributed over all issues based on their weight in the scopeor by a user who is not part of the Folio's team are not included. Refer to the Operational column description below to learn how these are taken into account. | | Effort Cost | Issue effort Effort logged , on issues by team membermembers, multiply multiplied by the their wage of the member at the date of the effort was logged. | | Operational | The operational expenses/revenues regroup the lodge expenses/revenues, the effort not associated with any issues. It is distributed over all issues based on their weight All other expenses allocated to that issue. These include non human resource costs (such as material, etc.) and effort that is not synchronized with JIRA's work log. These expenses are distributed over all issues proportionally to their Earned Value weight (as determined by their Earned Value Field) in the scope. Note that overtime Overtime cost distribution for synchronized with JIRA team member is slightly different since these costs are distributed on issue on witch which team member has logged time | | Planned | Issue planned cost Total folio planned cost distributed over all issues based on their weight in the scope. | | ∆ | Delta between Actual Issue Cost and Planned Issue Cost |
Report Parameters 
| For | Determines which financial data source to use. Actual Cost displays folio's Issues actual cost.
Actual Revenue displays folio's Issues actual revenues cost |
|---|
| Label | This allows you to display cost of issues for the selected Jira Issue Label. (not available at the portfolio level)
Only expenses with the specified label will be use to calculate issue cost Note : see Using Labels for more info on. |
|---|
| Issue Types | Issue types to be displayed in the report |
|---|
| Printable | Display a printable version of the report
Note that you can also use the shortcut "p" |
|---|
| Export to Excel | Export report to Excel |
|---|
| More Reports | Bring you back to Reporting List
Note that you can also use the shortcut "x" |
|---|
Selecting the "Printable" item in the report's action menu found at the top right of the report's parameters panel to get a printer-friendly version of the report. 
| Anchor |
|---|
| ExportToExcel |
|---|
| ExportToExcel |
|---|
|
Export to ExcelThe Issus Cost report can be exported to Excel format. It will give you all the latitude you need to further digest, analyze or graph the data. Do it by selecting the "Export to Excel" item in the report's action menu found on the top right of the report's parameters panel. The parameters that were used to generate the report can be found on the second tab of the generated spreadsheet 
|