Planning Sync for Jira (Tempo Integration) - User Manual
This guide explains how to install, set up, and operate Planning Sync for Jira (Tempo Integration).
It focuses on the admin experience and the common happy path setup.
This manual is intended for:
Jira administrators who install and configure the app
Space admins who need to understand what the automation does
What the app does
Planning Sync keeps Jira work item fields aligned with Tempo plan data. After setup, normal usage follows this pattern:
Tempo plans are created or updated
The app updates Jira fields based on your mappings
Optionally the plan data is forwarded to an external system
Installation and setup
After installation, open the Planning Sync admin page and follow the wizard.
Planning Sync requires a Tempo product. Install Timesheets by Tempo or Capacity Planner by Tempo before running the wizard.
Step one: Confirm Tempo
First make sure you have Tempo Timesheets or Tempo Capacity Planner installed.
The app checks for a Tempo app on the site.
If the check is inconclusive, you can still continue and validate later.
Step two: Authentication
Choose one of the following authentication methods:
OAuth 2.0, which is recommended for longer term use
Tempo API token, which is simple and quick
Tempo API token
In Jira, go to Apps → Tempo → Settings
Open API Integration
Select New Token, name it, and copy the token (it’s only shown once)
Paste the token into the Planning Sync Authentication step as API Token
Save the credentials in the app.
OAuth 2.0
In the Planning Sync app, copy the Callback URL
In Jira, go to Apps → Tempo → Settings
Open OAuth 2.0 Applications
Select New Application, name it, enter the Planning Sync Callback URL as the redirect URI and choose Client type Confidential
Copy the Client ID and Client Secret
Save the credentials
In the Planning Sync Authentication step
Paste the Client ID and Client Secret
Save the credentials
Click the Authorize button and complete the Tempo consent screen
Once authorization completes, the app will confirm that the connection is active.
Step three: Webhook URL
Review the webhook URL from the admin UI. It should automatically register with Tempo for webhooks on created, updated, and deleted events.
Step four: License status
The app reads your Marketplace license.
Advanced features are available only with the Advanced edition.
Once these steps are complete, move to configuration and enable the required listeners.
Configuration options
Event listeners
Control which events should be processed.
Tempo plan events: plan.created, plan.updated, plan.deleted
Tempo worklog events, optional
Jira work item events, optional
If a listener is turned off, the app will ignore that event type.
Field mapping from Tempo to Jira
Map Tempo plan data into Jira fields:
Latest plan end date mapped to a date or datetime field
First plan start date mapped to a date or datetime field
Plan assignee mapped to a user picker field
Behavior notes:
When no plans remain, the mapped date fields are cleared.
For the first plan start date, you can choose between upcoming plans only or all plans.
Field mapping from Jira to Tempo
Enable Jira to Tempo sync if you want Jira field updates to modify Tempo plans.
Jira plan start date mapped to Tempo plan start date
Default assignee mapped as a Tempo plan assignee fallback
This sync runs only when the Jira listener is enabled.
Global scope
Limit which work items are eligible for automation.
Allowlist by space
Allowlist by work type
When enabled, only allowed spaces and work types are processed.
Plan approvals
Control when plans require approval.
Required reviewer
Threshold for older plan end dates
Optional auto-approval rules
When approval requirements are not met, the plan is skipped and the action is logged.
Outbound destinations (Advanced edition)
Forward Tempo events to external systems.
Add one or more HTTPS destinations
Optional shared secret for request verification
Choose which Tempo events to forward
Select the payload mode, either raw Tempo data or custom JSON
If a destination fails, the app will attempt retries and record failures in the audit logs.
Audit logs (Advanced edition)
Review recent actions and webhook activity.
Admin page provides a full audit log
Space tab provides a space-scoped log for Planning Sync actions
Troubleshooting
If something appears incorrect, check:
Listener toggles
Field mapping configuration
Global scope allowlist
Audit log entries for errors or skips
Troubleshooting tips
If there are no updates in Jira:
Confirm the Tempo webhook is registered and enabled
Ensure the relevant listener is enabled
Check global scope allowlist settings
If the audit log is empty:
Confirm you are using the Advanced edition
Generate new events after enabling the feature
If there are webhook verification errors:
Verify the shared secret in Tempo matches the stored secret
Confirm the webhook URL is current for the environment
Where to find pages
Admin UI
Jira settings, then Apps, then Planning Sync
Space planning log
Jira space navigation, then Planning Log