Table of contents
Atlassian Setup
WorkSights connects to Jira through Atlassian's OAuth framework. Once connected, Jira delivers issue activity to WorkSights via webhooks for all mapped users. Setup takes a few minutes and requires Jira administrator privileges.
WorkSights supports Jira Cloud. Confluence is not supported because Atlassian removed webhook capabilities for that product.
For an overview of how Jira activity appears in WorkSights, see Atlassian Overview.
Connecting Atlassian
Step 1: Start the Connection
- Go to Services in the top navigation
- Find Atlassian in the list
- Click Connect Atlassian
Only Admins, Executives, and Owners in WorkSights can initiate this connection. The Jira account used to authorize 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 to allow WorkSights to receive webhook notifications for supported Jira events.
Once approved, WorkSights completes the configuration and activates webhook delivery automatically.
You will return to WorkSights and see the newly created Jira connection.
Step 3: User Mapping
WorkSights imports Jira users and attempts to match them to WorkSights profiles by email.
Open the Users tab to review mappings. For any user that did not map automatically, select the correct WorkSights user from the dropdown to complete the mapping.
Only mapped Jira users will have their activity displayed in WorkSights.
What Happens Next
Once the connection is established and users are mapped, WorkSights begins receiving Jira webhook events for issue creation, updates, and comments.
Activity appears on the timeline for mapped users from this point forward. No historical data is imported. User mappings and integration settings can be reviewed and updated at any time from the integration page.