...
To define a Bulk Job, select “Bulk Jobs” menu in OnLink and click on Add New. Then select the source data - you use select Tempo if you’re using that app or simply JQL to define the JQL that pulls worklogs.
...
Tempo
Here’s the configuration for TempoOnLink pulls approved timesheets for selected teams and periods from Tempo. Users can optionally supplement Tempo timesheet and worklog data from JSM Assets as well Jira issues before pushing data to target systems like Workday Time Tracking.
Here are the steps to configure Tempo 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: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: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:
|
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. |
JQL
Here’s the configuration for JQL.
...