Skip to content

docs(jira): clarify Jira Cloud transition comment screen dependency (#1623) - #1628

Merged
sooperset merged 2 commits into
sooperset:mainfrom
teddiesloco:fix/jira-transition-comment-fallback
Aug 28, 2026
Merged

sooperset merged 2 commits into
sooperset:mainfrom
teddiesloco:fix/jira-transition-comment-fallback

Conversation

@teddiesloco

@teddiesloco teddiesloco commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Fixes #1623.

Clarifies both the lower-level transition_issue docstring and the jira_transition_issue MCP parameter documentation that, on Jira Cloud, bundled transition comments (update.comment) require the workflow transition screen to include a Comment field. If Jira omits the comment, callers should use jira_add_comment to record it separately.

Regenerates the MCP tool reference and adds a schema regression test so the warning remains visible to tool callers.

Test Plan

  • uv run pytest tests/unit/jira/test_transitions.py -q (30 passed)
  • uv run pytest tests/unit/servers/test_jira_server.py -q -k transition_issue (4 passed)
  • uv run pytest tests/unit/test_generate_tool_docs.py -q (28 passed)
  • uv run python scripts/generate_tool_docs.py --check
  • Repository-equivalent Ruff, format, and mypy checks on changed Python files

@sooperset
sooperset merged commit e04ce75 into sooperset:main Aug 28, 2026
8 checks passed
@mcp-atlassian-maintainer

Copy link
Copy Markdown
Contributor

The transition-screen caveat now reaches both library users and MCP tool callers, and the schema test will keep it there. Thanks for spotting and documenting this, @teddiesloco.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jira_transition_issue's comment argument silently dropped on Jira Cloud (transition succeeds, comment never posts)

2 participants