eazyBI for Jira
eazyBI has integration with two Tempo apps for Jira, Tempo Timesheets and Tempo Planner. If any of those apps are installed on Jira then, in eazyBI Import options, tab Add-ons, you will see the import options for Tempo.
Jira Cloud access
eazyBI uses Tempo REST API Tempo data import. Specify Tempo API user access token from the API integration page granting eazyBI access to data with Tempo API during import. Option to add Tempo access token will be available if you have Tempo Timesheets or Tempo planner installed in your Jira.
eazyBI will import any values in default measure Hours spent for Jira site with enabled Tempo Timesheets only if Tempo API Token will be enabled.
Tempo Timesheets is a time tracking and reporting solution that seamlessly integrates with jira to help software, IT, service desk, and business teams and managers track time for accounting, payroll, client billing, enhanced efficiency, and forecasting.
If you have the Tempo Timesheets app installed then in eazyBI Jira import options tab Add-ons you will see the import options for Tempo Timesheets data.
Measures for logged hours
|Hours spent||The default measure Hours spent represents data from Tempo Timesheets.|
|Tempo billed hours||The measure is available if you select option to Import billed hours  in eazyBI for Jira server. Tempo billed hours are imported by default in eazyBI for Jira Cloud by enabling Tempo API Access token if you have Tempo Timesheets add-on.|
Dimensions for worklogs and custom fields
Tempo Timesheets worklog attributes
|Select worklog attributes  from a selection list. eazyBI will generate a new worklog dimension for any selected worklog attribute with a naming pattern Tempo <attribute name>, for example, Tempo Account. Worklog attribute dimensions work with measures Hours spent and Tempo billed hours only. eazyBI imports only these attribute types: Account, Checkbox, and Static list.|
|Account||The Tempo custom field  Account represents an account assigned to Jira issue (issue field "Account").|
|Team||The Tempo custom field  Team represents a team assigned to Jira issue (issue field "Team").|
|Tempo Category||Tempo custom field Tempo Category  is created based on the custom field Account attribute Category.|
Tempo custom field Tempo Customer  is created based on the custom field Account attributes Customer.
Logged by Team
Dimension represents teams of worklog users. Dimension Logged by Team is created by default when at least one of the specific Tempo import options is selected - tempo billed hours, tempo timesheet worklog attributes, tempo planned hours.
Logged by Team dimension is available on Jira Cloud and starting from the eazyBI version 6.1 on Jira Server.
Dimension represents the approval status of the worklogs . The Hours spent are split by status after worklogs are submitted for approval.
Timesheet Status dimension is available on Jira Cloud and starting from the eazyBI version 6.6 on Jira Server/Datacenter.
Dimension represents the reviewer to whom the worklogs were submitted .
Timesheet Reviewer dimension is available on Jira Cloud and starting from the eazyBI version 6.6 on Jira Server/Datacenter.
Tempo Planner data import is available on Jira Cloud and starting from the eazyBI version 6.1 on Jira Server.
Tempo Planner is a tool to manage resources and capacity in Jira and provides a real-time view of all resources, as well as their status and plans.
If you have the Tempo Planner add-on installed then in eazyBI Jira import options tab Add-ons you will see the import options for Tempo planner data.
Select checkbox for Tempo Planned import and specify period for plans you would like to import into eazyBI for data analysis.
|Tempo planned hours|
Measure "Tempo planned hours" is created for a specified time period (historical and future). Data for older periods are removed automatically.
Use measure with dimensions Time, Logged By user, and Logged by Team. eazyBI supports data import for planned time on issues and projects. Planned time on Projects will be mapped to Project dimension and any dimension with the project level. Planned time on issues will be mapped by any default Jira field and custom field dimension.
Check out some Tempo Planner use-cases and report examples in the Learn More section.
Tempo Required hours
Data import for Tempo required hours is available on Jira Cloud and starting from the eazyBI version 6.5 on Jira Server.
Select the checkbox for Tempo Required hours import and specify the period for required hours you would like to import into eazyBI for data analysis.
|Tempo Required hours|
Measure "Tempo Required hours" is created for a specified time period (historical and future) based on the workload scheme assigned to the user. Data for older periods are removed automatically. Required hours are imported only for users who have logged hours in the specified period.
Use measure with dimensions Time, Logged By, and Logged by Team.
If you selected the Import sample reports option, then additional sample reports are created in the Samples Time Tracking folder. Please try these reports to see which measures would be useful for your specific needs. Check out Learn More section for a detailed description of each report, how it is created, and what those metrics represent.
If you want to customize some reports, save them and change the name (as the default sample reports are overwritten during each Jira import).