Jira Update Issue Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
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.
Configuration Options
The following table summarizes the configuration options available for the jira-update-issue-sink
Kamelet:
Dependencies
At runtime, the jira-update-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-update-issue-sink"
You can now run it directly through the following command
camel run route.yaml