Linear and Jira tickets from any pattern#
Open a ticket from a pattern and Incident Knowledge keeps it in step. Each pattern gets one ticket per tracker, the assignee travels with it, and every lifecycle event (a fix attempt, a regression, a verified fix) is appended to the ticket description so the person on call reads the whole history in the tool they already use.
Fix Now explores and plans before it writes code#
Fix Now runs in two phases. The first reads the codebase around the stack trace and produces a written fix plan; the second resumes the same session and carries out that plan. The fix must come with a regression test that reproduces the failure, and when a run cannot produce a fix it says why and lists the next steps to take by hand.
A daily incident digest in Slack#
Turn on the digest in Slack settings and each morning brings new patterns grouped by severity, with a one-line headline for every P1 and the fixes that were verified overnight. Every item deep-links to its row in Incident Knowledge, as do the links on pull requests and the dashboard.
Improvements#
- Incident KnowledgePatterns and Clusters now have their own sub-tabs.
- Incident KnowledgeFilter patterns by confidence, with a 24-hour default range.
- Incident KnowledgeLog variants show as a collapsible section on each fault row.
- Incident KnowledgeFix Now lets you choose which log variants the fix should cover.
- Incident KnowledgeCopy any incident row straight into the Workbench.
- CLINew `entelligence incident` commands bring patterns into your terminal and your coding agent.
Fixes#
- Incident KnowledgeFix jobs whose webhook was missed now catch up on their own.
- Incident KnowledgeA fix that fails after merge is marked ineffective right away.
- Incident KnowledgeClosed Fix Now jobs no longer crowd the monitoring tab.