Monitor Issues

Warestack tracks every GitHub issue in real time, linking it with associated data.
It also enriches this data with metadata coming from your custom checks. Read more ↗.

How it works

1. Collects signals to detects every update (status, labels, comments, linked PRs) in real time.
2. Correlates discussions from Slack and issues from Linear or Jira.
3. Runs checks of your defined patterns (e.g., issue label required etc.).
4. Reports insights in the Warestack dashboard or via API.

Example of a Warestack Issue

This is an example of a typical GitHub issue enriched with metadata, associated activity, and automated checks powered by Warestack. In this case, an active check detected missing labels and triggered a notification.

{
"type": "GitHub Issue",
"title": "feat(manage-checks): enable inline edit for checks",
"metadata": {
  "author": "steliosot",
  "repository": "core-api",
  "status": "Open",
  "updated": "1 day ago"
},
"description": "Enable inline editing for checks from the Manage Checks page. Use a small modal to update description, condition, or severity.",
"checks": [
  {
    "rule": "Label required",
    "details": "Add one like 'enhancement' or 'help wanted'."
  },
  {
    "rule": "Stale issue detection",
    "details": "Issue is stale for more than 5 days."
  }
],
"associated_pull_request": {
  "title": "feat(checks): add inline edit modal and PATCH endpoint"
},
"associated_workflow_run": {
  "name": "build-and-test.yml",
  "status": "passed successfully",
  "run_id": 154
},
"slack_summary": {
  "channel": "#dev-core",
  "message": "Team confirmed inline edit feature improves setup flow. Implementation scheduled for next sprint."
},
"summary": "This Warestack issue shows how all related activities—PRs, workflows, and discussions—are unified into a single view. Teams gain complete traceability and reduce manual coordination."
}

Suggested checks

• flag issues closed without linked PRs

  Ensures that every closed issue has an associated code change, avoiding dead-tickets.

• notify when issue is stale for more than X days

  Helps teams detect and clear issues that haven’t seen activity in a set period — reducing backlog noise.

• alert if issue assignee changed after merge

  Catches post-merge ownership changes that might indicate accountability gaps or process skips.

• block issue re-close if linked deploy/tests failed

  Prevents closing issues before code changes, builds, or tests linked to them are validated, ensuring quality closure.