Jira Transition Issue Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
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.
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.
Configuration Options
The following table summarizes the configuration options available for the jira-transition-issue-sink
Kamelet:
Dependencies
At runtime, the jira-transition-issue-sink
Kamelet relies upon the presence of the following dependencies:
-
camel:core
-
camel:jackson
-
camel:jira
-
camel:kamelet
-
mvn:com.fasterxml.jackson.datatype:jackson-datatype-joda:2.12.5
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camel
Supposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:jira-transition-issue-sink"
You can now run it directly through the following command
camel run route.yaml