Claudio Miranda created CAMEL-19587:
---------------------------------------
Summary: camel-jira: optional header field IssueAssignee doesn't
work
Key: CAMEL-19587
URL: https://issues.apache.org/jira/browse/CAMEL-19587
Project: Camel
Issue Type: Improvement
Components: camel-jira
Affects Versions: 3.21.0
Reporter: Claudio Miranda
There is a bug in the Jira rest client library, where calling the
\{{builder.setAssigneeName(assigneeName)}} in [jira
component|https://github.com/apache/camel/blob/camel-3.21.x/components/camel-jira/src/main/java/org/apache/camel/component/jira/producer/AddIssueProducer.java#L107]
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
