Bulk Jobs

Owned by Girish Reddy
Last updated: Dec 09, 2024
2 min read

Use Bulk Jobs functionality to pull data from Jira (using JQL) and push to target web services (e.g. Workday Timesheet).

Here’s how you can define a bulk job. OnLink keeps track of last time the job ran, so you can use smart values like {last_successful_rundate} or {last_successful_runtime} in your JQL. OnLink will automatically replace these values with actual date or date-time values are run time.

image-20241210-002600.png

You can use a JQL to return all issues that have worklogs you want to process. A couple of examples:

  1. worklogDate >= startOfWeek(-1) AND worklogDate <= endOfWeek(-1) - pulls all worklogs entered last week i.e., Monday, 12:00 AM of the prior week to Sunday, December 3, 2024, at 11:59 PM.

  2. worklogDate >= {last_successful_rundate} - use the last successful date managed by OnLink.

Using option 1 is preferable as all worklogs entered for previous week are captured. This assumes that employees do not go back more than one week in the past to enter time. This can be changed to month or other dates as per customer’s requirements.

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.

image-20241209-225342.png

The {worklog.author.accountId.getid('workspaceid', 'asset object name', 'atlassian user object name')} can be used to reverse map Jira User ID to Workday ID. This mapping is driven from JSM Assets object that maps Jira User to Workday ID. Note that the Workday ID field should be the label on the object. To get the Workspace ID, you can run this URL: https://yourinstancename.atlassian.net/rest/servicedeskapi/assets/workspace