
Table of contents
GitHub Issues
GitHub issues are used to plan work, report tasks and track progress. Because GitHub models issues and pull requests with the same underlying structure, WorkSights receives issue events through the same webhook system but displays them separately for clarity.
WorkSights receives issue metadata and the text of comments. Issue body text is never received.
For connection steps, see GitHub Setup. For how GitHub activity appears more broadly, see GitHub Integration Overview.
What WorkSights Receives
WorkSights ingests the following 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 It Appears in WorkSights
Issue activity appears as structured timeline entries showing the repository, issue title, the event that occurred and the timestamp. Comments appear as GitHub Comment on {repo} #{n}, with the full comment body in the activity detail, the same way as comments on pull requests.
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 does not appear.
Troubleshooting
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 do not appear.
For persistent issues, contact us through the support chat (Help in the user menu) or at [email protected].