Repository navigation
docs(jira): clarify Jira Cloud transition comment screen dependency (#1623) - #1628
Merged
sooperset merged 2 commits intoAug 28, 2026
Merged
Conversation
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. |
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
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.
Summary
Fixes #1623.
Clarifies both the lower-level
transition_issuedocstring and thejira_transition_issueMCP 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 usejira_add_commentto 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