Table of contents
Atlassian Integration Overview
WorkSights's Atlassian integration supports Jira. Issue creation, updates, and comments appear as structured activity on each user's timeline in the Code category, alongside GitHub activity.
Confluence is not currently supported. Confluence has no REST webhook API, which is the mechanism WorkSights uses to receive activity in real time. WorkSights will expand Atlassian coverage as API capabilities allow.
For connection steps, see Atlassian Setup.
What WorkSights Receives
WorkSights captures issue creation, field-level updates including status, assignee, priority, title, and other standard fields, and comments added to issues by mapped users. Comment events include a preview of the comment text.
WorkSights does not import issue body content, worklogs, attachments, sprint data, or any content beyond the fields included in Jira’s webhook payloads. No historical data is imported on connect.
WorkSights imports Jira users and matches them to WorkSights users by email address. Once a user is mapped, their Atlassian account ID becomes the stable key WorkSights uses to attribute their future activity. Atlassian hides user email addresses by default, so many webhook events carry an account ID and display name but no email.
When a user is already mapped, their activity flows normally. When a user is not yet mapped and the webhook does not include an email, WorkSights cannot auto-create the mapping and the event is skipped. Enabling email visibility in your Atlassian workspace settings resolves this for new events.
There is no ClientSights path for Atlassian. Jira activity is a WorkSights-only signal.
Keeping the Connection Current
WorkSights automatically keeps your Jira webhook subscription current in the background, so there is nothing to renew or reconnect under normal operation. If Atlassian ever revokes the connection's authorization outright, you'll need to reconnect — in that case, you'll be notified.
Integration Page Overview
The Atlassian integration page contains three tabs:
- Overview - Connection details and integration owner
- Users - Jira users mapped to WorkSights users
- Connections - Connected Jira sites
Troubleshooting
No activity at all after connecting
Confirm users are mapped in the Users tab. If auto-mapping failed, check whether Atlassian email visibility is enabled in your workspace settings. Without an email in the webhook payload, WorkSights cannot auto-map users and their events are skipped. Also confirm the activity occurred after the connection was established, as no historical data is imported.
Some users have activity but others don’t
Atlassian hides email addresses by default. Users whose webhooks do not include an email cannot be auto-mapped. Enable email visibility in Atlassian workspace settings, or map affected users manually in the Users tab.
Confluence activity is missing
Confluence is not supported. Confluence has no REST webhook API, so WorkSights cannot receive activity from it at this time.
Activity is delayed
This is expected. Activity is captured in real time and processed in batches roughly every 20 minutes.
Multiple activities appearing for one issue
This is expected. Each field change in a Jira update carries a distinct changelog ID and appears as a separate activity entry.