Skip to main content

Improve Linear sub-issue import behaviour

Feature Request

When importing issues from Linear, parent issues and sub-issues are currently shown as a flat list with no visible hierarchy. This makes it hard to understand which issues belong together and adds friction when trying to mirror a Linear issue structure inside Locu

What would help

  • Show sub-issues nested or indented beneath their parent issue during import

  • Allow importing all sub-issues automatically when a parent issue is imported

Too Much Friction
Right now, importing a parent issue with its related sub-issues is more manual than it should be. The current workflow (for me) feels too fragmented:

  • Find each issue separately in the list

  • Import issues one by one

  • Manually reorganise them afterward in Locu

Posted by squeakyvermin ·
Status: Planned1 comment

Log in to comment and vote

Comments1

  • Locu

    Team•

    Aug 24

    Hey, yes this makes sense. Once we enable time tracking on breakdown steps (request), we should improve the import as well.

    Few questions:

    1. Linear allows multi-level hierarchy. Sub-issues can have their own sub-issues. Would you expect the import to bring in the whole subtree?

    2. Our current thinking: you can import an issue together with all its sub-issues at once, keeping the hierarchy, and you can still import any sub-issue on its own as a top-level task in Locu. One detail: if you already imported a sub-issue as top-level and later import its parent with the tree, we'd keep your task where it is and skip it in the import (you can nest it manually anytime). Does that match what you'd expect?

    3. Issue updates (state, name, priority) will keep syncing automatically as they do today, but we're not planning to auto-sync structure for now: sub-issues added or reparented in Linear later would be picked up by re-running the import on the parent, and your structure in Locu always wins. Is hierarchy at import time enough to enable your workflow?

    Thanks!