Budgety
eazyBI for Jira
Budgety for Jira is a project budget management and cost tracking tool developed by Deiser.
Data import from Budgety is available on eazyBI for Jira Cloud.
On this page:
Budgety data import
If you would like to import Budgety data please enable the import in eazyBI site settings and define the API endpoints to retrieve Budgety data.
- In Jira, go to Budgety → three-dot menu in top right corner → API Documentation.
- Find the respective documentation section and expand it to copy the path for GET method:
- API Key → Create a new JWT and copy the endpoint for
api_token_endpoint - Budgets → Get budgets and copy the endpoint for
get_budgets_endpoint - Costs → Get costs by budget and copy the endpoint for
get_costs_by_budget_endpoint
- API Key → Create a new JWT and copy the endpoint for
- Add the copied endpoints in eazyBI site settings:
[jira.budgety] api_token_endpoint = "..." get_budgets_endpoint = "..." get_costs_by_budget_endpoint = "..."
When the eazyBI site settings are added, a new section, Budgety, is available in the eazyBI import options tab, Add-ons.
eazyBI uses API keys to get data from Budgety.
- In Jira Cloud, go to the Budgety → three-dot menu in the top right corner → API Integrations and create an API key.
- Enter the created key and key ID in the eazyBI import options.
Dimensions
Yuo can use some of the Jira standard dimensions to analyse Budgety data.
Project | A project directly linked to the Budget. |
|---|---|
Issue | An issue directly linked to the Budget. |
Logged by | A user who logged the hours applicable to the cost. |
Worklog | A worklog record which is applicable to the cost. |
The following Budgety-specific dimensions are available.
Budgety Assignee | A user assigned to the cost if a cost is not based on logged work. |
|---|---|
Budgety Budget | A budget name. |
Budgety Capital Type | A capital types of each Cost - CAPEX, OPEX, or (none). |
Budgety Cost | A cost name. The cost key is appended in brackets if several costs have the same name. eazyBI creates a secondary hierarchy By name that groups costs by name (without cost key) and then by specific costs, thus allowing the analysis of all costs with the same name across all budgets. |
Budgety Directness Type | Direction type of each Cost - Direct, Indirect, or (none). |
Measures
The following Budgety-specific measures are available.
Budgety Budgets created | Budget count. When used with the Time dimension, data are grouped by the budget creation date. |
|---|---|
Budgety Costs created | Cost count. When used with the Time dimension, data are grouped by the cost creation date. In the report, the user can interact with the measure and Drill through Budget and Drill through Cost to see the exact budget and cost behind the value. |
Budgety Target budget | Target budget for the Budget. When used with the Time dimension, data are grouped by the budget creation date. In the report, the user can interact with the measure and Drill through Issues to see list of linked issues of the budget. |
Budgety Hours spent | Logged hours of the users assigned to the cost based on logged work. When used with the Time dimension, data are grouped by the worklog start date. In the report, the user can interact with the measure and Drill through Worklogs to see the exact logged time entries or Drill through Budget and Drill through Cost to see the exact budget and cost behind the value. |
Budgety Total cost | Total value of costs calcauted by Budgety based on each cost parameter's rates and logged work or units. When used with the Time dimension, data are grouped by worklog start date or cost date that is not based on logged work. In the report, the user can interact with the measure and Drill through Budget and Drill through Cost to see the exact budget and cost behind the value. |
Budget Cost per target % | Cost per target percentage is calculated as the total cost (see measure Budgety Total cost) divided by the target budget of the Budget. |
Properties
The following Budgety-specific properties are available.
Budgety Cost budget | A budget name of a cost. This is a cost property and should be used together with the Budgety Cost dimension. |
|---|---|
Budgety Cost start date | A from date of a cost that is based on logged work or the date of a cost that is not based on logged work. This is a cost property and should be used together with the Budgety Cost dimension. |
Budgety Cost end date | An until date of a cost that is based on logged work. This is a cost property and should be used together with the Budgety Cost dimension. |
Budgety Cost per hour | A cost per hour of a cost that is based on logged work. This is a cost property and should be used together with the Budgety Cost dimension. |
Budgety Cost per unit | A cost per unit of a cost that is not based on logged work. This is a cost property and should be used together with the Budgety Cost dimension. |
Budgety Cost units | A count of units to a cost that is not based on logged work. This is a cost property and should be used together with the Budgety Cost dimension. |
Sample reports
If you selected the Import sample reports option, then additional sample reports are created in the Samples Budgety folder. Please try these reports to see which measures would be useful for your specific needs. If you would like to customize some reports, then save them as a new report version and change the name (as the default sample reports are overwritten during each Jira import).
