Using Jira Cloud With Tempo Timesheets
If you use the Tempo Timesheets Jira plugin, the worklogs are not stored in the Jira database. It is therefore necessary to retrieve the worklogs from a different REST endpoint.
Use Tempo Timesheets with caution. The Tempo Worklog API is currently marked as experimental and has some shortcomings compared to the original Jira worklogs:
- No support for paging: Be aware of operation issues if there are more than 2000 worklogs per week.
- No support for changed or deleted worklogs: You must re-import all worklogs to circumvent this limitation.
JustOn does not guarantee the correct operation of the Jira integration with Tempo Timesheets.
Setting up Jira Connector for a Jira instance that integrates Tempo Timesheets involves the following specific tasks:
- Configuring a specific setting for the Jira connection
- Adding a Tempo user access token to Salesforce
Configuring Jira Connection
The JIRA Connection custom setting requires the following specific information:
||Must be set to
|Last Upsert Refresh||not empty||Must be set before the first import. Must be set to a date before the first Tempo worklog in order to retrieve all worklogs.|
|Batch Size||Set this to a number between 200-500 if you expect many worklogs per week.|
|Shift Date/Time by Hours||Tempo reports the date/time values in the user's time zone. If your Salesforce instance uses a different time zone, you must specify a correction value to adjust the date/time values.|
Adding Tempo User Access Token
Generate a new Tempo user access token in your Jira account.
Make sure your Tempo plugin is properly installed, then open Tempo > Tempo Settings > Create User Token.
Copy the token.
- In your Salesforce org, open the Tempo API Token page.
- Paste the token.
- Click Save.