Tempo worklogs integration
Overview
The Power BI Connector app integrates with Tempo Timesheets to help you analyze the Tempo data in Power BI Desktop. The integration enables you to pull the Tempo Worklog Attributes, Account Information, and Worklog information from Tempo Timesheets. To set up integration, refer to Tempo Timesheets.
You can export the following fields to analyze Tempo worklog data.
Enhancements and updates on cloud
The Power BI Connector app is enhanced to provide effective and accurate Tempo data. These enhancements apply to the cloud hosting of the app.
Worklog fields
The Connector Time Tracking (Worklogs) field list now includes the Tempo field Tempo: WorklogID.
The Worklog ID field has been renamed to Jira Worklog ID to distinguish it from the new Tempo field.
Worklog timestamps
If Tempo is integrated, all Tempo worklogs are now retrieved from Tempo instead of Jira.
The worklog timestamp is now displayed in the Jira user's timezone, as set in their Jira profile, for the following worklog fields: Worklog Creation Date, Worklog Last Update Date, and Time Entry Date.
If the Jira user timezone visibility is set either to the organization’s name or only you, the Jira Default user time zone (global default timezone) will be used for the worklog timestamps.
To view and update Jira user’s timezone, navigate to Manage Account > Account preferences. Learn more.
To update your Jira profile and visibility settings, navigate to Manage Account > Profile and visibility. Learn more.
To view and update the Jira instance global timezone, you need Administrator privileges. Navigate to Settings > System > General configuration > Default user time zone. Learn more.
Frequently Asked Questions
What has improved in the worklog timestamps on the cloud?
Previously, the Power BI Connector app retrieved the timestamp from Jira, applied the data format changes, and displayed it in the Etc/UTC format. Now, If Tempo is integrated, the worklog timestamps are retrieved directly from Tempo, ensuring greater accuracy and consistency.
Example scenario:
A Jira user’s account timezone preference is set to US/Central and is visible to Anyone. When the Jira user logs time through Tempo, the worklog fields are displayed in the US/Central timezone.
Why is Worklog ID renamed to Jira Worklog ID?
With the addition of the Tempo: WorklogID field, the Worklog ID is renamed to Jira Worklog ID to ensure clear differentiation between Tempo and Jira worklog ID.
Is Tempo worklog data cached on the cloud?
Yes, Tempo worklogs are cached with a TTL (Time-to-Live) of 5 days on the cloud. However, the app manages additions, deletions, and updates to worklogs, even though worklogs are cached to ensure data accuracy.
If you need to refresh or reset the cache, go to the connector edit screen and select the Do not use cache for next refresh option. This resets all cached values of the connector, not just the worklogs.
Related content
Need support? Create a request with our support team.
Copyright © 2005 - 2025 Appfire | All rights reserved.