Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 34. Jira Transition Issue Sink

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.

34.1. Configuration Options

The following table summarizes the configuration options available for the jira-transition-issue-sink Kamelet:

Property	Name	Description	Type	Example
jiraUrl *	Jira URL	The URL of your instance of Jira	string	`"http://my_jira.com:8081"`
password *	Password	The password or the API Token to access Jira	string
username *	Username	The username to access Jira	string

Note

Fields marked with an asterisk (*) are mandatory.

34.2. 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.4.redhat-00001

34.3. Usage

This section describes how you can use the jira-transition-issue-sink.

34.3.1. Knative Sink

You can use the jira-transition-issue-sink Kamelet as a Knative sink by binding it to a Knative object.

jira-transition-issue-sink-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: jira-transition-issue-sink-binding
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  steps:
  - ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: insert-header-action
    properties:
      name: "issueTransitionId"
      value: 701
  - ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: insert-header-action
    properties:
      name: "issueKey"
      value: "MYP-162"
  sink:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
    properties:
      jiraUrl: "jira server url"
      username: "username"
      password: "password"

34.3.1.1. Prerequisite

Make sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.

34.3.1.2. Procedure for using the cluster CLI

Save the jira-transition-issue-sink-binding.yaml file to your local drive, and then edit it as needed for your configuration.

Run the sink by using the following command:

oc apply -f jira-transition-issue-sink-binding.yaml

34.3.1.3. Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind --name jira-transition-issue-sink-binding timer-source?message="The new comment 123"\&period=60000 --step insert-header-action -p step-0.name=issueKey -p step-0.value=MYP-170 --step insert-header-action -p step-1.name=issueTransitionId -p step-1.value=5 jira-transition-issue-sink?jiraUrl="jira url"\&username="username"\&password="password"

This command creates the KameletBinding in the current namespace on the cluster.

34.3.2. Kafka Sink

You can use the jira-transition-issue-sink Kamelet as a Kafka sink by binding it to a Kafka topic.

jira-transition-issue-sink-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: jira-transition-issue-sink-binding
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  steps:
  - ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: insert-header-action
    properties:
      name: "issueTransitionId"
      value: 701
  - ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: insert-header-action
    properties:
      name: "issueKey"
      value: "MYP-162"
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: jira-transition-issue-sink
    properties:
      jiraUrl: "jira server url"
      username: "username"
      password: "password"

34.3.2.1. Prerequisites

Ensure that you’ve installed the AMQ Streams operator in your OpenShift cluster and created a topic named my-topic in the current namespace. Make also sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.

34.3.2.2. Procedure for using the cluster CLI

Save the jira-transition-issue-sink-binding.yaml file to your local drive, and then edit it as needed for your configuration.

Run the sink by using the following command:

oc apply -f jira-transition-issue-sink-binding.yaml

34.3.2.3. Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind --name jira-transition-issue-sink-binding timer-source?message="The new comment 123"\&period=60000 --step insert-header-action -p step-0.name=issueKey -p step-0.value=MYP-170 --step insert-header-action -p step-1.name=issueTransitionId -p step-1.value=5 jira-transition-issue-sink?jiraUrl="jira url"\&username="username"\&password="password"

This command creates the KameletBinding in the current namespace on the cluster.

34.4. Kamelet source file

https://github.com/openshift-integration/kamelet-catalog/jira-transition-issue-sink.kamelet.yaml