Table of contents
Atlassian Integration Overview
WorkSights's Atlassian integration currently supports Jira.
Confluence is not ingested at this time. Atlassian removed webhook support for Confluence, which prevents WorkSights from receiving updates from that product. Jira remains fully supported, with issue creation, updates, and comments appearing as structured activity on each user's daily timeline.
Support for additional Atlassian products, including Bitbucket and Confluence, is planned as API capabilities evolve.
For connection steps, see Atlassian Setup.
What WorkSights Receives
WorkSights receives webhook events from Jira representing core issue-level activity:
- Issue creation: when a mapped user opens a new Jira issue
- Issue updates: changes to fields such as status, assignee, priority, title, or description
- Comments: comments added to Jira issues by mapped users
How Jira Activity Appears
Jira activity appears as structured timeline entries for each mapped user. Entries include a brief description of the event (for example, Created Jira issue or Updated Jira issue), the issue key, and the type of action performed. WorkSights treats these as execution-oriented work signals, giving teams a clear view of where time and effort are directed throughout the day.
Only mapped Jira users appear in WorkSights. Unmapped users are not displayed.
Why Only Jira?
Atlassian deprecated webhook support for Confluence, removing the mechanism WorkSights uses to receive activity notifications. Jira webhooks remain fully available. When Atlassian restores suitable event support for other products, WorkSights will expand coverage accordingly.
Integration Page Overview
The Atlassian integration page contains four tabs:
- Overview: connection details and integration owner
- Users: Jira users mapped to WorkSights users
- Features: visibility options for supported Jira event types
- Connections: connected Jira accounts
Data Notes
WorkSights does not import issue body content, WorkLogs, attachments, or any content-level information. Only lightweight metadata is used to surface visibility without exposing what's inside each issue.
Troubleshooting
If Jira activity is not appearing as expected:
- Confirm the affected Jira user is mapped to a WorkSights user in the Users tab.
- Verify that the authorizing Jira account has admin permissions.
- Confirm the activity occurred after the connection was established. No historical data is imported.
- Reconnect the integration if Jira permissions or tokens have changed.
- For persistent issues, contact support via the in-app chat.