Atlassian – Overview

WorkSights's Atlassian integration currently supports Jira.

Confluence is not ingested at this time because Atlassian removed webhook support for Confluence, which prevents WorkSights from receiving updates from that product. Jira remains fully supported, and WorkSights displays key Jira issue activity as part of each user's daily timeline.

The integration allows activity performed in Jira, such as creating, updating, or commenting on issues, to appear in WorkSights as structured activities. This gives teams clear visibility into where work is happening during the day and ensures Jira work is recognized alongside activity from other tools.

Future support for additional Atlassian products, including Bitbucket and Confluence, is planned as API capabilities evolve.

What WorkSights Receives from Jira

WorkSights receives webhook events from Jira that represent core issue-level activity:

Issue creation

When a mapped user creates a Jira issue.

Issue updates

Changes to issue fields such as status, assignee, priority, title, description, or other standard field modifications.

Comments

User-authored comments added to Jira issues.

WorkSights does not import issue bodies, WorkLogs, or any sensitive or content-level information. Only lightweight metadata is used to deliver visibility without exposing issue content or sensitive information.

Why Only Jira?

Atlassian deprecated webhook support for Confluence, which prevents WorkSights from receiving notifications for page edits, comments, or other activity from that product. Jira webhooks remain fully available and allow WorkSights to reflect a user's Jira work reliably.

When Atlassian restores suitable webhook or event support, WorkSights will expand integration coverage to additional Atlassian tools.

How Jira Activity Appears in WorkSights

Jira activity appears in WorkSights as structured timeline entries associated with the mapped user. These entries may include:

• A brief description of the event (for example Created Jira issue or Updated Jira issue)
• The issue key or issue title for context
• The type of Jira action performed

WorkSights treats these as execution-oriented work signals, helping teams understand where time and effort are directed.

Only mapped Jira users receive Jira visibility in WorkSights. Unmapped Jira users do not appear.

Integration Page Overview

The Atlassian integration page contains:

• Overview Tab — connection details and integration owner
• Users Tab — Jira users mapped to WorkSights users
• Features Tab — visibility options for supported Jira event types
• Connections Tab — connected Jira accounts

Data Access and Privacy

WorkSights receives only lightweight activity metadata from Jira:

• Issue creation
• Issue field updates
• Comments linked to mapped users
• Issue summaries or titles for context

WorkSights does not ingest:

• Issue content or descriptions beyond the summary
• WorkLogs or time tracking data
• Attachments
• Confluence pages or comments
• Sensitive data or restricted fields

All data sent from Jira follows Atlassian's webhook permissions and product-level access controls.

Troubleshooting

If Jira activity is not appearing in WorkSights:

• Ensure Jira users are mapped correctly to WorkSights users.
• Confirm webhook permissions were granted during the OAuth connection.
• Verify that the activity was performed by a mapped user.
• Check that the issue event type is one of the supported Jira notifications.

For connection steps, see the Atlassian Setup Guide.