Table of contents
GitHub issues are used to plan work, report tasks, and track progress. Because GitHub models issues and pull requests using the same underlying structure, WorkSights receives issue-related events through the same webhook system but displays them separately for clarity.
WorkSights shows issue activity using metadata only, giving teams lightweight visibility into planning work without exposing issue content.
What WorkSights Receives
WorkSights ingests metadata when mapped users interact with issues:
- Issue created
- Issue edited (title changes)
- Issue closed
- Comments on issues
WorkSights does not ingest issue body text, labels, attachments, or custom fields.
How Issues Appear in WorkSights
Issue activity appears as structured entries showing:
- Repository
- Issue title
- The event that occurred
- Timestamp
Comments appear as metadata-only comment events without their text.
Data Details
Only mapped GitHub users generate issue activity.
Issue activity is available only after the integration is installed.
Issue content is never stored in WorkSights.
WorkSights does not ingest labels, milestones, or workflows.
Next Steps
For review comment-level collaboration on issues, see GitHub Comments.
For configuration steps and permissions, see GitHub Setup.
For a platform-level explanation of GitHub activity, see GitHub Overview.