Table of contents
WorkSights reflects core Jira issue activity so teams can understand where execution work is happening throughout the day.. When mapped users create or update issues in Jira, WorkSights receives lightweight metadata and displays it as structured activity on the timeline. This provides clear visibility into ongoing team work while keeping Jira content private.
What WorkSights Receives
WorkSights ingests Jira webhook events related to issue lifecycle activity. These include:
- Issue creation, when a new issue is opened by a mapped user
- Issue updates, such as changes to status, assignee, priority, or title
- Standard field changes included in Jira's webhook payloads
WorkSights uses only the metadata Jira provides through its webhook payloads and does not ingest full issue content.
How Jira Issues Appear in WorkSights
Each supported Jira event appears as its own activity entry for the mapped user on their WorkSights timeline. Entries include a short description of the change, along with the issue key and summary for context. This makes it easy to understand where work occurred without navigating away from WorkSights.
Notes and Limitations
WorkSights intentionally limits Jira ingestion to high-level metadata.
WorkSights does not ingest:
- WorkLogs or Jira time tracking entries. (Any duration shown in WorkSights is generated by WorkSights's own activity model, not imported from Jira.)
- Full issue descriptions or detailed field content
- Attachments
- Activity from unmapped Jira users
- Any Confluence activity
Only fields included in Jira's webhook payloads are available for display.
User Mapping Requirements
Jira activity appears only for users who are mapped correctly in the Atlassian integration. If a Jira user is not mapped to a WorkSights user, their issue creation and updates will not appear. Mapping should be reviewed after connecting Jira and whenever new Jira users join the team.
Data Access and Privacy
WorkSights ingests only the metadata required to provide context, following Jira's permission boundaries. Sensitive or content-level information is not imported, and WorkSights does not access data beyond what the authorizing Jira admin can view.
Summary
With Jira connected and users mapped, WorkSights provides clear visibility into issue creation and updates while maintaining strong privacy boundaries. Teams receive an accurate picture of execution work without exposing full Jira content.
For comment-level activity, see Jira Comments.