-
Notifications
You must be signed in to change notification settings - Fork 663
fix(jira): fix type for Jira issue descriptions #8559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…based on JIRA version
… Cloud and Server versions
…on and enhance error handling
|
I'm testing locally, and not work for all scenarios, reading the documentation others field can be text rich. |
…ription type for comments
Thanks for the review! This fix covers all rich text fields (Issue.Description, Comment.Body, Worklog.Comment) that can cause the ADF unmarshaling error, including Epic descriptions since they use the Issue struct. The FlexibleDescription type handles both string and ADF formats with full backward compatibility. If you encounter specific scenarios that don't work, please share the error details. |
davinogueiradev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I did some tests and passed them all
klesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This fix #8558 ensures that the Jira plugin no longer throws JSON deserialization errors when encountering rich-text descriptions, allowing the pipeline to continue running smoothly. Existing string-only descriptions remain fully supported, guaranteeing backward compatibility.