Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Linear MCP plugin: parent label group not found despite existing [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45410•Fetched 2026-04-09 08:06:04
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
esetnikesetnik
Participants
esetnikesetnik
Timeline (top)
labeled ×3

The label "release" simultaneously:

  • Exists (step 1 — can't create due to duplicate name)
  • Doesn't exist (step 2-3 — not returned by list)
  • Can't be referenced (step 4 — not found as parent)

Error Message

Result: Error: Duplicate label name - Label "release" already exists in team <team>. Result: Error: Parent label "release" not found If a label exists (proven by the duplicate name error), it should appear in list_issue_labels results and be usable as a parent when creating child labels.

Root Cause

The label "release" simultaneously:

  • Exists (step 1 — can't create due to duplicate name)
  • Doesn't exist (step 2-3 — not returned by list)
  • Can't be referenced (step 4 — not found as parent)

Fix Action

Workaround

Created the label with a colon-separated name (release:v6.11.4) instead of using the parent-child relationship.

Code Example

Tool: mcp__plugin_linear_linear__create_issue_label
Parameters: { "name": "release", "isGroup": true }

---

Tool: mcp__plugin_linear_linear__list_issue_labels
Parameters: { "name": "release" }

---

Tool: mcp__plugin_linear_linear__list_issue_labels
Parameters: { "limit": 250 }

---

Tool: mcp__plugin_linear_linear__create_issue_label
Parameters: { "name": "v6.11.4", "parent": "release", "color": "#26b5ce" }
RAW_BUFFERClick to expand / collapse

Bug

The Linear MCP plugin's label operations are inconsistent when a label group exists but isn't returned by list_issue_labels.

Steps to Reproduce

1. Attempt to create a label group

Tool: mcp__plugin_linear_linear__create_issue_label
Parameters: { "name": "release", "isGroup": true }

Result: Error: Duplicate label name - Label "release" already exists in team <team>.

This confirms a label named "release" exists.

2. Try to find it via list

Tool: mcp__plugin_linear_linear__list_issue_labels
Parameters: { "name": "release" }

Result: {"labels":[], "hasNextPage": false}

Also tried with team parameter — same empty result.

3. List all labels (no filter)

Tool: mcp__plugin_linear_linear__list_issue_labels
Parameters: { "limit": 250 }

Result: Returns 5 labels (none named "release").

4. Try to create a child label under the parent

Tool: mcp__plugin_linear_linear__create_issue_label
Parameters: { "name": "v6.11.4", "parent": "release", "color": "#26b5ce" }

Result: Error: Parent label "release" not found

Summary

The label "release" simultaneously:

  • Exists (step 1 — can't create due to duplicate name)
  • Doesn't exist (step 2-3 — not returned by list)
  • Can't be referenced (step 4 — not found as parent)

Expected Behavior

If a label exists (proven by the duplicate name error), it should appear in list_issue_labels results and be usable as a parent when creating child labels.

Workaround

Created the label with a colon-separated name (release:v6.11.4) instead of using the parent-child relationship.

Environment

  • Claude Code with plugin:linear:linear MCP server

extent analysis

TL;DR

The most likely fix is to investigate and resolve the inconsistency in the list_issue_labels API, ensuring it returns all existing labels, including those that are label groups.

Guidance

  • Verify the list_issue_labels API implementation to ensure it correctly handles label groups and returns all existing labels.
  • Check the database or storage to confirm the "release" label group exists and is properly configured.
  • Test the list_issue_labels API with different parameters, such as team and limit, to identify any potential filtering or pagination issues.
  • Consider modifying the create_issue_label API to handle cases where the parent label is not returned by list_issue_labels, potentially by using a different method to verify the parent label's existence.

Example

No code snippet is provided as the issue does not contain sufficient information about the API implementations.

Notes

The provided workaround of using a colon-separated name instead of a parent-child relationship may not be a suitable long-term solution, as it bypasses the intended label hierarchy.

Recommendation

Apply a workaround, such as the colon-separated name approach, until the underlying issue with the list_issue_labels API can be resolved, to ensure label consistency and usability.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING