Table of contents
Connecting Atlassian Jira to WorkSights is a quick process that enables WorkSights to receive issue activity through Jira's webhook framework. Once connected, WorkSights reflects issue creation, updates, and comments for all mapped Jira users.
WorkSights supports Jira Cloud. Confluence is not supported because Atlassian removed webhook capabilities for that product. Only Jira sends activity signals to WorkSights.
Step-by-Step Setup Instructions
Step 1 – Start the Connection in WorkSights
- Go to Services in the top navigation.
- Find Atlassian in the list.
- Select Connect Atlassian.
You must be an Admin, Executive, or Owner in WorkSights to initiate this integration. On the Jira side, the user authorizing the connection must have Jira administrator permissions.
Step 2 – Authorize WorkSights in Jira
WorkSights redirects you to Jira's OAuth authorization flow.
Approve the requested permissions, which allow WorkSights to receive webhook notifications for supported Jira events. Once approved, WorkSights completes the system configuration and activates webhook delivery.
After authorization is finished, you will return to WorkSights and see the newly created Jira connection.
Step 3 – Map Jira Users to WorkSights Users
WorkSights automatically imports Jira users and attempts to match them to WorkSights users by email. To review or complete mappings:
- Open the Users Tab in the Atlassian integration
- Select any unmapped Jira user
- Choose the correct WorkSights user to complete the mapping
Only mapped Jira users will have their Jira activity displayed in WorkSights. Unmapped users will not appear.
What Happens Next
After the connection is established and users are mapped, WorkSights begins receiving Jira webhook events for issue creation, updates, and comments. Activity starts to appear on the timeline for mapped users.
No historical data is imported. Only events that occur after connection will appear.
You can update user mappings or disconnect the integration at any time from the integration page.
For issue-level activity, see Jira Issues.
For comment-level activity, see Jira Comments.
Troubleshooting
If Jira activity does not appear:
- Confirm the Jira user is mapped to a WorkSights user.
- Verify the Jira authorizing account has the correct admin permissions.
- Ensure the activity occurred after the connection was established.
- Reconnect the integration if Jira permissions or tokens have changed.