Table of contents
Jira Issues
WorkSights reflects core Jira issue activity so teams can see 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.
For connection steps, see Atlassian Setup.
What WorkSights Receives
WorkSights ingests Jira webhook events for issue lifecycle activity:
- Issue creation: when a mapped user opens a new Jira issue
- Issue updates: changes to status, assignee, priority, title, or other standard fields
- Standard field changes: included in Jira's webhook payloads
How Issues Appear
Each issue event appears as its own activity entry on the mapped user's timeline. Entries include a short description of the change, the issue key, and the issue summary for context.
Data Notes
Full issue descriptions, WorkLogs, time tracking data, and attachments are never received. Any duration shown in WorkSights is generated by WorkSights's own activity model and is not imported from Jira. Only fields included in Jira's webhook payloads are available. Activity appears only for mapped users and only after the connection is established.
Troubleshooting
If Jira issue activity is not appearing as expected:
- Confirm the affected Jira user is mapped to a WorkSights user in the Users tab.
- 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.