Last updated
November 12th, 2026

Atlassian Setup

WorkSights connects to Jira through Atlassian's OAuth framework. Once connected, Jira delivers issue activity to WorkSights through webhooks for all mapped users. Setup takes a few minutes. Only Owners, Executives and Admins can connect services, and the Jira account you authorize with must have Jira administrator permissions.

WorkSights supports Jira Cloud. Confluence is not supported, as it has no REST webhook API.

For an overview of how Jira activity appears in WorkSights, see Atlassian Integration Overview.

Connecting Atlassian

Step 1: Start the Connection

  1. Go to Services in the top navigation
  2. Find Atlassian in the list
  3. Click Connect Atlassian
Atlassian card on the WorkSights Connected Services page

Step 2: Authorize WorkSights in Jira

You are redirected to Jira's OAuth authorization flow. Approve the requested permissions to let WorkSights read issue and user data and manage webhooks. Once approved, WorkSights registers the webhook and returns you to the integration page.

If your Atlassian account has access to multiple sites, you select which site to connect. Each site connects separately. Repeat the process to connect additional sites.

Step 3: Map Users

WorkSights imports Jira users and matches them to WorkSights users 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.

Mapping an Atlassian user to a WorkSights profile

Atlassian hides user email addresses by default. When a webhook does not include an email, WorkSights cannot create the mapping, and that user's events are skipped until they are mapped manually or email visibility is enabled in Atlassian workspace settings.

What Happens Next

Once connected and users are mapped, WorkSights begins receiving Jira activity for issue creation, updates, and comments. Activity appears on the timeline within about 20 minutes, from this point forward. No historical data is imported.

Overview tab of the Atlassian service in WorkSights

WorkSights keeps the Jira webhook subscription current in the background. Reconnect the integration if Jira permissions or tokens change. If Atlassian revokes the connection's authorization outright, you are notified and need to reconnect.

You can review and update user mappings and connection settings at any time from the integration page.

Related Guides

Atlassian Overview

Jira Issues

Jira Comments