Jira Comments

WorkSights reflects Jira comments as part of a user's visible work activity. Comments represent meaningful collaboration and issue-level engagement, so when a mapped Jira user adds a comment, WorkSights receives a metadata signal and displays it on the timeline. This gives teams a clearer picture of contribution patterns throughout the day without exposing the content of the comment itself.

What WorkSights Receives

WorkSights ingests Jira webhook events that indicate when a mapped user has added a comment to an issue. The signal includes:

• The fact that a comment was added
• The associated issue key
• The issue summary when available
• The identity of the commenting user (for mapping and attribution)

WorkSights does not ingest the text of the comment. Only metadata is used to provide context and attribution.

How Comments Appear in WorkSights

Each supported comment event appears as its own activity entry for the mapped user. WorkSights displays a short, standardized description (for example, Commented on Jira issue), along with the issue key and summary so users can quickly understand where the collaboration occurred. Because WorkSights does not ingest comment content, no message body or detailed text appears in the timeline.

Comments appear in sequence with other Jira events, contributing to a clear view of engagement and flow of work across the day.

Notes and Limitations

WorkSights intentionally limits Jira comment ingestion to high-level metadata. WorkSights does not ingest:

• The comment text or message body
• Jira WorkLogs or Jira time tracking
• Attachments
• Comments authored by unmapped users
• Any Confluence activity

Only supported Jira webhook fields are used, and Jira's permission model determines which metadata is available.

User Mapping Requirements

A comment is attributed in WorkSights only if the Jira user who authored it is mapped to the corresponding WorkSights user. If a comment is made by an unmapped Jira user, it will not display that activity. Mapping should be reviewed after connection to ensure all active Jira users are included.

Data Access and Privacy

WorkSights uses only the minimal metadata required to show that a comment occurred. The content of the comment is never imported, stored, or displayed. All visibility respects Jira's permission boundaries and the capabilities of the webhook system.

Summary

WorkSights provides clear visibility into Jira comment activity by displaying comment events as structured timeline entries while keeping all comment content private. This helps teams understand collaboration patterns and effort distribution without exposing sensitive information.

For issue-level activity, see Jira Issues.