See How Much Unplanned Work Derails You
New urgent issues added mid-sprint? Notis logs them so you can measure how much unplanned work actually derails your sprints with real data.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Execute ClickHouse Query
Execute a sql query in clickhouse and return the results. this is the primary action for querying data from clickhouse databases.
Why this helps
Sprints get disrupted by unplanned urgent work, but you don't measure it. You feel like you're context-switching constantly, but you can't prove it to the team.
- Auto-log mid-sprint additions to measure disruption impact
- Data-driven conversations about scope creep and planning discipline
- Visibility into which sprints get hit hardest by unplanned work
Setup
Build it in a few focused steps.
- 1Connect Linear and ClickHouse to Notis.
- 2Tell Notis: 'When an issue is added to an active sprint after sprint start, log it to my disruption table as unplanned work.'
- 3Notis uses Issue Updated trigger and filters for sprint changes during active sprints.
- 4Pick Slack or email for notifications.
- 5Test by adding an issue mid-sprint and checking your disruption table.
Questions about this workflow
How does Notis know when a sprint is active?
Tell Notis your sprint schedule, like 'Sprints start Monday, end Friday.' It knows what's active and what's not.
What if issues are moved between sprints?
Notis can log moves as disruption too, if you want. Tell it what counts as 'unplanned' for your team.
Can this help prevent future disruption?
Yes. Once you see 5 unplanned issues derailed last sprint, you can protect this sprint better. Data drives behavior change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to ClickHouse. A trigger fires from one place; an action lands in another.
Linear triggers
ClickHouse actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute ClickHouse Query
Execute a sql query in clickhouse and return the results. this is the primary action for querying data from clickhouse databases.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Database Schema
Get comprehensive schema overview of an entire database including all tables and optionally their column definitions. essential for ai agents to understand the complete database structure in a single call.
Comment Received Trigger
Triggered when a comment is received.
Get Table Schema
Get detailed schema information for a specific table including column definitions, types, keys, and optionally sample data. this is essential for ai agents to understand table structure before constructing queries.
Issue Created Trigger
Triggered when a new issue is created.
List ClickHouse Databases
List all databases in the clickhouse instance. useful for discovering available databases before querying tables.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List ClickHouse Tables
List tables in clickhouse databases. returns information about tables including their engine, size, and row count.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and ClickHouse, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business ClickHouse.