docs(cli): fix Jira CLI card to reflect direct Atlassian REST API access#1364
Merged
Conversation
The Jira CLI card claimed gaia jira works "via the MCP bridge," but
handle_jira_command runs gaia.apps.jira.app directly ("no MCP needed")
and the Jira guide states it talks to the Atlassian REST API with no
bridge required. The --mcp-host/--mcp-port options remain valid for the
optional MCP integration, so they stay in the options table.
Contributor
|
One-line change, correctly targeted: the Jira card description was factually wrong, and this fixes it to match both the code path ( SummaryA single-character-budget fix that removes a misleading "via the MCP bridge" claim that would have sent users down a needless MCP setup path. The replacement — "using your Atlassian credentials (REST API)" — matches the Jira guide verbatim and reflects the actual Issues FoundNone. Strengths
VerdictApprove. No blocking issues. The fix is correct, minimal, and consistent with |
4 tasks
kovtcharov
approved these changes
Jun 3, 2026
kovtcharov-amd
pushed a commit
that referenced
this pull request
Jun 3, 2026
Resolve conflicts in CLAUDE.md and docs/reference/cli.mdx by taking main's versions: PRs #1337, #1340, #1364 already synced both files to the code more recently, and the PR's stale side reintroduced removed commands (mcp add/remove) and the broken /guides/summarize link that was failing the internal cross-reference CI check. Keep the PR's still-valid accuracy fixes (Gemma-4-E4B-it default in chat/llm/emr docs, agent-ui Lemonade port 13305 + #install anchor, code agent Python-gen still supported, telegram.mdx removal, #606 stale-note removal). Fix one contradiction the merge surfaced: main's CLAUDE.md and emr/cli.py listed the EMR VLM as Qwen3-VL-4B, but agent.py and all --vlm-model defaults are Gemma-4-E4B-it-GGUF. Aligned both with the code and emr.mdx.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this matters
A review comment on the merged #1337 (review) flagged a docs-accuracy bug: the new Jira CLI card said
gaia jiraworks "via the MCP bridge." That's wrong and could send users down a needless setup path. The code path (handle_jira_command→ importsgaia.apps.jira.appdirectly, comment: "no MCP needed") and the Jira guide ("communicates directly with the Atlassian REST API — no intermediary services or MCP bridge required") both contradict the card. This aligns the card with the code and the guide.The
--mcp-host/--mcp-portflags are a real optional integration (they exist in thejirasubparser), so they remain in the options table — only the high-level description changed.Test plan
docs/reference/cli.mdxJira section now reads "using your Atlassian credentials (REST API)" and matchesdocs/guides/jira.mdx.gaia jira -hstill lists--mcp-host/--mcp-port(options table unchanged).