Support parent/child issue filtering in `issues list`

[dubscode]

Summary

Please add a first-class way to list child issues for a parent issue from the CLI.

This came up while cleaning up Linear sub-issues where issue titles are used to create branch names. The parent issue was easy to fetch directly, but listing only its children required falling back to other tooling because linear issues list does not currently expose parent/child filtering.

Repro

Using @wiseiodev/linear-cli 1.4.0 on Node 24.15.0:

linear issues list --help

The command-specific help only shows:

Usage: linear issues list [options]

List issues

Options:
  -h, --help  display help for command

Global help exposes --team, --limit, and --cursor, but no parent/child filters.

I also tried the obvious candidates:

linear issues list --parent BB-418 --json
linear issues list --parentId b37232f9-d6c8-4502-8da0-867aa39bc9a0 --json
linear issues list --children BB-418 --json

Each returns an unknown option error.

Expected behavior

One of these shapes would make the workflow straightforward:

linear issues list --parent BB-418 --json
linear issues list --parent-id BB-418 --json
linear issues children BB-418 --json

Ideally the flag would accept both a Linear identifier like BB-418 and the internal UUID, matching how linear issues get <id> works.

Actual behavior

issues list appears to support pagination only. Looking at the installed dist/index.js, the issues.list handler passes only:

{
  limit: globals.limit,
  cursor: globals.cursor,
}

to listIssues(...), and toListVariables(...) only maps those to first / after for client.issues(...).

Why this matters

Sub-issues often need batch maintenance: retitling, reprioritizing, checking status, or creating branches. Since this CLI already has linear issues branch <id> and JSON output, parent/child filtering would make it much easier for agents and scripts to operate on the exact child set without broad workspace scans or direct GraphQL fallbacks.

Nice-to-have follow-ups

• Include parentId or parent identifier in issue list/get JSON output.
• Consider --no-parent for top-level issues only.
• If command-specific help intentionally omits global flags, consider showing inherited flags in linear issues list --help, since that was the first place I checked.

[dubscode]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Add first-class parent/child issue filtering for linear issues list.

Current behavior:
Users can list issues, but cannot directly narrow the list to children of a parent issue or to top-level issues only. Attempts such as --parent, --parent-id, or --children are not accepted.

Desired behavior:
linear issues list should support filtering by parent issue, accepting both Linear identifiers like BB-418 and internal UUIDs where practical. It should also support listing top-level issues only.

Key interfaces:

• The issue list query/options shape should include parent filtering and top-level-only filtering.
• Normalized issue records should expose enough parent metadata for the filter to be testable.
• CLI help for issue listing should document the new filters.

Acceptance criteria:

• linear issues list --parent <identifier-or-id> --json returns only children of the referenced parent issue.
• linear issues list --parent-id <identifier-or-id> --json is either supported as an alias or intentionally rejected with documented help that points to the supported flag.
• linear issues list --no-parent --json returns only top-level issues.
• Human and JSON output continue to respect existing pagination options.
• Tests cover parent filtering, top-level filtering, and help output.

Out of scope:

• Batch-updating child issues.
• Adding every possible Linear hierarchy field beyond what this filter needs.
• Changing the existing issues get behavior except where needed to resolve parent references.

[dubscode]

This was generated by AI during triage.

Closed as completed by merged PR #18: #18