> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear on Vortex IQ

> Monitor Linear performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Linear performance signals, run automated checks, and prepare approved work through Vortex IQ.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=linear)

<CardGroup cols={5}>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="1">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (19 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                               |
        | ----------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Mean days from `started` to `completed` - how fast work clears once picked up.                                               |
        | **Avg Lead Time (days)**            | Merchant rule      | Mean days from `createdAt` to `completedAt` - full time-in-system.                                                           |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Mean days from finding-issue creation to completion - Linear's richest cycle-time read.                                      |
        | **Backlog by Priority**             | Merchant rule      | Open issues grouped by priority - skew toward Urgent/High flags a firefighting backlog.                                      |
        | **Backlog by Status**               | Watch only         | Open issues grouped by Linear state.type - the queue's shape at a glance.                                                    |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Issues labelled blocked / flagged blocked - the operational queue's stuck list.                                              |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle time split by priority - Urgent should clear fastest.                                                                  |
        | **In Progress**                     | Watch only         | Issues in the `started` state - work an engineer has actively pulled.                                                        |
        | **Oldest Open (days)**              | Merchant rule      | Age in days of the oldest open issue - backlog-rot signal.                                                                   |
        | **Open Tickets**                    | Merchant rule      | Linear issues with state.type ∈ {triage, backlog, unstarted, started} across connected teams - top-of-funnel backlog volume. |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | Engineers with >10 open issues - capacity-bottleneck and single-point-of-failure candidates.                                 |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Issues added to the active cycle after it started - reactive vs proactive signal.                                            |
        | **Sprint Progress**                 | Alert band 80 / 50 | Active Linear cycle completion fraction - burn against the cycle commitment.                                                 |
        | **Sprint Velocity (avg)**           | Merchant rule      | Issues completed per cycle averaged over the last 5 cycles - the team's capacity ceiling.                                    |
        | **Throughput Trend**                | Watch only         | 30-day completion trend - the slope of the team's output.                                                                    |
        | **Tickets Resolved (7d)**           | Merchant rule      | Issues moved to completed in the last 7 days vs the prior week.                                                              |
        | **Tickets by Assignee**             | Merchant rule      | Open issue count per engineer - where the queue concentrates.                                                                |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Open issues with no assignee - work nobody owns yet.                                                                         |
        | **VortexIQ Findings In Progress**   | Watch only         | Findings an engineer has actively pulled (state.type = started).                                                             |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15  | Open findings whose updatedAt hasn't moved in 14+ days - on Linear's cycle-driven culture this is a louder signal than other PM tools.                 |
        | **Finding Resolution Rate (90d)**         | Alert band 75 / 50 | Share of findings created in 90d that reached completed/canceled. \<50% is the universal floor; on Linear, \<65% is already early warning.             |
        | **VortexIQ Findings Open**                | Merchant rule      | Issues we filed from audit findings still open (label vortex-iq-finding, state.type not completed/canceled) - the live backlog of things VortexIQ surf |
        | **VortexIQ Findings Resolved**            | Watch only         | Findings resolved (completed or canceled) in the last 90 days.                                                                                         |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time finding here goes stale from that moment, silently, until someone notices the numbers stopped updating.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **1 write** operations across graphqls on Linear. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=linear)

    #### Ready to build your first Linear workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | graphqls | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>