# Linear Jira personal-account link before assignee drift

> Have each user connect their own Jira account before dual-run sync so assignee and creator fields keep pointing to the right person.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/linear-jira-personal-account-link-before-assignee-drift/
- 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, Product, Developer Tools
- Stages: dual-run trial, identity mapping, migration, trust


## Why this can grow

A dual-run trial loses credibility fast when ownership fields start lying. Linear's Jira docs call out the failure mode clearly: without personal account links, assignees can end up unassigned and created-by fields can collapse onto the setup user. Once that happens, the new workspace looks less like a live planning tool and more like a lossy mirror. Fixing identity mapping early makes the trial believable enough for real work to move over.

## 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 jira personal-account link before assignee drift can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Migration and Product 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 recommends that each user connect a personal Jira account for better handling of fields like Assignee and Creator, and notes that without a connection the assignee can be unassigned or the creator can appear as the user who configured Jira.

## Adjacent tactics in the same lane

- [Linear JQL webhook filter before sync flood](/growth-ideas/linear-jql-webhook-filter-before-sync-flood/) - same source, 2 shared channels, 2 shared stages
- [Dual-run sync during trial before full Jira cutover](/growth-ideas/dual-run-sync-during-trial-before-full-jira-cutover/) - same source, 1 shared channel, 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
- [Linear top-level team import before sub-team polish](/growth-ideas/linear-top-level-team-import-before-subteam-polish/) - 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.