Jira
The Jira origin reads data from a Jira instance. For information about supported versions, see Supported Systems and Versions.
The Jira origin requires that Data Collector use Java version 17. For more information, see Java Version.
When you configure the Jira origin, you configure the Jira instance to send the request to, the authentication scheme to use for the request, and the parameters of the request.
You can optionally use a proxy server and configure TLS properties.
Event Generation
The Jira origin can generate events that you can use in an event stream. With event generation enabled, the origin generates event records each time the origin completes processing all available data.
- With the Pipeline Finisher executor to
stop the pipeline and transition the pipeline to a Finished state when
the origin completes processing available data.
When you restart a pipeline stopped by the Pipeline Finisher executor, the origin continues processing from the last-saved offset unless you reset the origin.
For an example, see Stopping a Pipeline After Processing All Available Data.
- With a destination to store event information.
For an example, see Preserving an Audit Trail of Events.
Event Records
Event records generated by the Jira origin have the following event-related record header attributes. Record header attributes are stored as String values:
Record Header Attribute | Description |
---|---|
sdc.event.type | Event type. Uses one of the following types:
|
sdc.event.version | Integer that indicates the version of the event record type. |
sdc.event.creation_timestamp | Epoch timestamp when the stage created the event. |
- finished
- The origin generates a finished event record when the origin finishes reading data from the instance.
- no-more-data
- The Jira origin generates a no-more-data event record when the origin completes processing all data returned by all queries.
- start
- The origin generates a start event record when the origins starts reading data from the instance.
OAuth 2 Authentication
The Jira origin can use the OAuth 2 protocol to connect to a Jira instance that uses basic or digest authentication, OAuth 2 client credentials, OAuth 2 username and password, or OAuth 2 access token.
The OAuth 2 protocol authorizes third-party access to resources without sharing credentials. The Jira origin uses credentials to request an access token from the service. The service returns the token to the origin, and then the origin includes the token in a header in each request to the Jira instance.
- Client credentials grant
-
The stage sends its own credentials - the client ID and client secret or the basic authentication credentials - to the Jira instance.
For more information about the client credentials grant, see https://tools.ietf.org/html/rfc6749#section-4.4.
- Access token grant
-
The stage sends an access token to an authorization service and obtains an access token for the Jira instance
- Owner credentials grant
-
The stage sends the credentials for the resource owner - the resource owner user name, password, client ID, and client secret - to the Jira instance.
For more information about the resource owner password credentials grant, see https://tools.ietf.org/html/rfc6749#section-4.3.
Configuring a Jira Origin
Configure a Jira origin to read data from a Jira instance.
This origin is a Technology Preview feature. It is not meant for use in production.