[CAMEL-19587] camel-jira: optional header field IssueAssignee doesn't work

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.21.0
• Fix Version/s: 3.20.7, 3.21.1, 3.22.0, 4.0-RC2, 4.0.0
• Component/s: camel-jira
• Estimated Complexity: Unknown
• Assignee: Claudio Miranda
• Reporter: Claudio Miranda
• Created: 06/Jul/23 12:12
• Updated: 07/Jul/23 06:07
• Resolved: 07/Jul/23 06:07

Description

There is a bug in the Jira rest client library, where calling the builder.setAssigneeName(assigneeName) in jira component doesn't work, as it seems the jira rest api (backend) evolved to not support setting the field with name attribute.

Community Discussion:
https://community.developer.atlassian.com/t/creating-jira-issue-with-custom-assignee-in-jira-cloud-fails-with-account-not-found/27683

https://community.developer.atlassian.com/t/connect-app-create-issue-using-rest-api-with-jwt-authorization/32505
 
However it worked when setting the field with the account id attribute.

For a standalone server installation, using the name attribute works.

Issue Links

• links to: Github PR 10602 (main branch)
• links to: GitHub Pull Request #10610
• links to: GitHub Pull Request #10612
• links to: GitHub Pull Request #10613