Content Comparison

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_monthweek

Set to pull periods to processbe processed.

Set it to the keywords previous_month week or previous_week month to automatically pull relevant previous week or month 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.

Note that OnLink processes only one period per execution. For example, when previous_month is selected OnLink processes one week in previous month at a time. It keeps track of which period it already processed. If running manually, wait for previous execution to complete and trigger a new execution.

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:

1. workspace id - use the link in help text to get the workspace ID

2. object name - name of your assets object

3. 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

{WorkerAssetsDataworkerAssetsData/asset attribute}

Use this syntax in the target message mapping to map object attribute. Each field mapped this way is considered required.

{worklogIssueFields/customfield_10134}

Use this syntax in the target message mapping to map issue fields. Each field mapped this way is considered required.