Table of contents
GitHub Issues
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 events through the same webhook system but displays them separately for clarity.
WorkSights ingests metadata only. Issue body text and content are never received.
For connection steps, see GitHub Setup.
What WorkSights Receives
WorkSights ingests metadata when mapped users interact with issues:
- Issue created
- Issue edited (title changes)
- Issue closed
- Comments on issues
Issue body text, labels, attachments, milestones, and custom fields are never received.
How Issues Appear
Issue activity appears as structured timeline entries showing the repository, issue title, the event that occurred, and the timestamp. Comments appear as metadata-only entries without their text.
Data Notes
Issue activity appears only for mapped GitHub users and only from repositories included in the GitHub App installation scope. Activity created before the integration was installed will not appear.
Troubleshooting
If issue activity is not appearing as expected:
- Confirm the affected user is mapped to their GitHub username in the Users tab.
- Check that the repository is included in the GitHub App installation scope.
- Issues created before the integration was installed will not appear.
- For persistent issues, contact support via the in-app chat.