Fix ADF description parsing for Jira Cloud #782
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.
Jira Cloud's new editor returns description and comment body fields as Atlassian Document Format (ADF) JSON objects instead of plain strings. This was causing Pydantic validation errors when searching issues.
Changes:
Fixes validation error: "Input should be a valid string [type=string_type,
input_value={'type': 'doc', ...}]"
🤖 Generated with Claude Code
Description
Fixes: #
Changes
Testing
[briefly describe]we have tested it on our MCP server. Can now search for issues.Checklist