Importing Tempo Worklogs to Workday Time Tracking

[#1]

Happy New Year! As we kick off 2025, we’re excited to explore new ways to optimize enterprise workflows, starting with time tracking. In this blog, we’ll walk you through integrating worklogs from Jira into HR and time tracking systems like Workday. Let’s dive in.

Use Case Overview:

For many enterprises, Jira serves as the go-to platform for managing work. Whether through native Jira functionality or third-party tools like Tempo, timesheets are often created to capture time spent on tasks. However, this data must eventually flow into HR or accounting systems for purposes like invoicing, workload analysis, or performance evaluation.

The challenge: Streamlining the integration of Jira worklogs or Tempo timesheets into systems like Workday without manual intervention.

The solution: Leveraging OnLink’s Bulk Job functionality to seamlessly transfer this data.

Introducing OnLink’s Bulk Jobs Feature:

The Bulk Jobs feature in OnLink allows you to pull data from Tempo (using its API) or Jira Worklogs (via JQL) and push it to target systems like Workday Time Tracking.

How to Define a Bulk Job

• Navigate to the “Bulk Jobs” menu in OnLink and click “Add New.”
• Select the source data: Choose Tempo if using Tempo Timesheets.
• Use JQL to define the criteria for pulling worklogs from Jira.

Tempo Timesheets Integration

OnLink simplifies the process by pulling approved timesheets for selected teams and periods from Tempo. Users can even enrich this data with additional information from Jira issue fields or JSM Assets before pushing it to the target system.

Configuration Steps

Here’s how to configure Tempo as your source:

Attribute	Description
config:teams=all	Set to pull teams from Tempo, set it to “all” to pull all teams from Tempo Can also be set to a comma separated string to pull a few specific teams e.g. config:teams=9283,9230
config:periods=previous_month	Set to pull periods to process. Set it to keywords previous_month or previous_week to automatically pull relevant periods. Can also be set to a specific period e.g. config:periods=2024-01-01,2024-01-07 where 2024-01-01 is from date and 2024-01-07 is end date.
config:worker_aql=workspace id|object name|filter attribute	The “worker_aql” can optionally be used to pull any data attributes from JSM Assets. This pulls data based on Jira user filter. Set three attributes for this configuration: workspace id - use the link in help text to get the workspace ID object name - name of your assets object attribute - name of object attribute of type Atlassian user, used as filter condition
filter:timesheet_approval_status=APPROVED	Set this to filter Tempo timesheets - in this example, only APPROVED timesheets will be processed
filter:worklog_attributes_key=activity|development,design	Set this to filter worklogs - in this example, only those worklogs that have the “activity” attribute set to development or design will be processed
{WorkerAssetsData/asset attribute}	Use this syntax in the target message mapping to map object attribute.
{worklogIssueFields/customfield_10134}	Use this syntax in the target message mapping to map issue fields.

Once configured, this data is automatically mapped and pushed to Workday using message mapping syntax like:

• {WorkerAssetsData/asset attribute}
• {worklogIssueFields/customfield_10134}

Jira Worklogs Integration Using JQL

For users without Tempo, JQL offers a flexible way to pull worklogs directly from Jira.

Configuration Examples:

1. Worklogs from last week:

worklogDate >= startOfWeek(-1) AND worklogDate <= endOfWeek(-1)

2. Worklogs since the last run:

worklogDate >= {last_successful_rundate}

Mapping Jira to Workday IDs

To align Jira users with Workday IDs:

• Use {worklog.author.accountId.getid('workspaceid', 'asset object name', 'atlassian user object name')} for reverse mapping.
• The mapping references JSM Assets that link Jira User IDs to Workday IDs.

You can specify the webservice request body as shown below. If {worklog.<field>} is used, then OnLink will automatically pull all worklog entries, as each issue can have more than one worklog.

End to End Demo

Upcoming Features:

• Worklogs to UKG
• Worklogs to BambooHR
• Worklogs to ADP
• Worklogs to Snowflake

If you are looking to integrate timesheets data from Jira to HR/Accounting systems, please give OnLink a try and let us know your feedback.