camel-jira-update-issue-sink-kafka-connector sink configuration

Connector Description: Update fields of an existing issue in Jira. The Kamelet expects the following headers to be set: - `issueKey` / `ce-issueKey`: as the issue code in Jira. - `issueTypeName` / `ce-issueTypeName`: as the name of the issue type (example: Bug, Enhancement). - `issueSummary` / `ce-issueSummary`: as the title or summary of the issue. - `issueAssignee` / `ce-issueAssignee`: as the user assigned to the issue (Optional). - `issuePriorityName` / `ce-issuePriorityName`: as the priority name of the issue (example: Critical, Blocker, Trivial) (Optional). - `issueComponents` / `ce-issueComponents`: as list of string with the valid component names (Optional). - `issueDescription` / `ce-issueDescription`: as the issue description (Optional). The issue description can be set from the body of the message or the `issueDescription`/`ce-issueDescription` in the header, however the body takes precedence. To authenticate a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.

When using camel-jira-update-issue-sink-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:

  <!-- use the same version as your Camel Kafka connector version -->

To use this sink connector in Kafka connect you’ll need to set the following connector.class


The camel-jira-update-issue-sink sink connector supports 4 options, which are listed below.

Name Description Default Priority


Required The URL of your instance of Jira Example:



The username to access Jira.



The password to access Jira.



Personal Token.


The camel-jira-update-issue-sink sink connector has no converters out of the box.

The camel-jira-update-issue-sink sink connector has no transforms out of the box.

The camel-jira-update-issue-sink sink connector has no aggregation strategies out of the box.