Files
Iulia Bejan 3a6a6f6682
Docker / build (push) Has been cancelled
GoReleaser Release / release (push) Has been cancelled
MCP Server Diff / mcp-diff (push) Has been cancelled
Publish to MCP Registry / publish (push) Has been cancelled
CodeQL / Analyze (go) (push) Has been cancelled
CodeQL / Analyze (actions) (push) Has been cancelled
CodeQL / Analyze (javascript) (push) Has been cancelled
Build and Test Go Project / build (macos-latest) (push) Has been cancelled
Build and Test Go Project / build (ubuntu-latest) (push) Has been cancelled
Build and Test Go Project / build (windows-latest) (push) Has been cancelled
Fix set_issue_fields mutation: use correct inline fragments for IssueFieldValue union (#2366)
* Fix set_issue_fields mutation: use correct inline fragments for IssueFieldValue union

The mutation response struct used a single inline fragment
'... on IssueFieldDateValue' with a 'Name' field that doesn't exist
on that type (only IssueFieldSingleSelectValue has 'name'). This
caused GraphQL validation to fail with:

  Field 'name' doesn't exist on type 'IssueFieldDateValue'

Since GraphQL validates the entire document (including response
selection sets) before executing any operation, the mutation never
fired at all — no fields were ever set regardless of input.

Fix by adding correct inline fragments for all four union types:
- IssueFieldTextValue (value)
- IssueFieldSingleSelectValue (name)
- IssueFieldDateValue (value)
- IssueFieldNumberValue (value)

* Update test mock to match corrected inline fragments

* Update handler_test.go formatting
2026-04-22 15:42:25 +01:00
..
2026-02-12 11:04:54 +01:00
2026-02-19 15:17:52 +00:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00
2026-01-06 17:38:12 +00:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00
2026-02-25 13:42:24 +00:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00
2026-02-12 11:04:54 +01:00