# Linear JQL webhook filter before sync flood

> Edit the Jira webhook with a JQL filter before sync goes live so the trial only pulls the issue classes you actually want to evaluate.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/linear-jql-webhook-filter-before-sync-flood/
- Source: [linear.app](https://linear.app/docs/jira)
- GrowthDex source hub: [Linear Docs: Jira](/sources/linear-docs-jira-linear-app/)
- Last checked: 2026-06-08T12:08:13.000Z
- Rarity: rare
- Budget: low
- Channels: Migration, Operations, Developer Tools
- Stages: dual-run trial, jira sync, migration, scope control


## Why this can grow

A sync trial gets noisy when every class of Jira work arrives in Linear at once. Linear gives teams a cleaner path: narrow the webhook itself with JQL so only the right issues create or update mirrored work. That keeps the evaluation surface focused on the jobs that matter and prevents the new tool from being judged by the legacy noise it never needed to inherit.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where linear jql webhook filter before sync flood can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Migration and Operations channel.
3. Use the evidence from linear.app to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Linear documents editing the Jira webhook and adding a custom JQL query in the Issue related events field so only issues that meet the filter sync into Linear, including issues that later change to match the rule.

## Adjacent tactics in the same lane

- [Linear Jira personal-account link before assignee drift](/growth-ideas/linear-jira-personal-account-link-before-assignee-drift/) - same source, 2 shared channels, 2 shared stages
- [Linear top-level team import before sub-team polish](/growth-ideas/linear-top-level-team-import-before-subteam-polish/) - 3 shared channels, 1 shared stage
- [Dual-run sync during trial before full Jira cutover](/growth-ideas/dual-run-sync-during-trial-before-full-jira-cutover/) - same source, 1 shared stage
- [Linear open-only pilot import before archive drag](/growth-ideas/linear-open-only-pilot-import-before-archive-drag/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The switch should look like current work before the cutover](/blog/the-switch-should-look-like-current-work-before-the-cutover/) - migration, project operations, developer tools

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.