camel-jira-transition-issue-sink-kafka-connector sink configuration
Connector Description: Sets a new status (transition to) of an existing issue in Jira. The Kamelet expects the following headers to be set: - `issueKey` / `ce-issueKey`: as the issue unique code. - `issueTransitionId` / `ce-issueTransitionId`: as the new status (transition) code. You should carefully check the project workflow as each transition may have conditions to check before the transition is made. The comment of the transition is set in the body of the message.
When using camel-jira-transition-issue-sink-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-jira-transition-issue-sink-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
To use this sink connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.jiratransitionissuesink.CamelJiratransitionissuesinkSinkConnector
The camel-jira-transition-issue-sink sink connector supports 3 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required The URL of your instance of Jira Example: http://my_jira.com:8081. |
HIGH |
||
Required The username to access Jira. |
HIGH |
||
Required The password or the API Token to access Jira. |
HIGH |
The camel-jira-transition-issue-sink sink connector has no converters out of the box.
The camel-jira-transition-issue-sink sink connector has no transforms out of the box.
The camel-jira-transition-issue-sink sink connector has no aggregation strategies out of the box.