PutJiraIssue

Description:

This processor creates issues on a Jira server or cloud service. A JSON with the issues definition must be provided as an incoming FlowFile.

Additional Details...

Tags:

jira, put, issue

Properties:

In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display Name	API Name	Default Value	Allowable Values	Description
Web Client Service Provider	web-client-service-provider		Controller Service API: WebClientServiceProvider Implementation: StandardWebClientServiceProvider	Controller service for HTTP client operations.
URL	jira-base-url			Base URL of Jira. Example: https://issues.apache.org/jira
Authentication Method	jira-authentication-method	None	None Access Token API Token	Method used to authenticate with Jira
Access Token	jira-personal-access-token			Personal access tokens (PATs) are a secure way to use scripts and integrate external applications with your Atlassian application. In Jira, select your profile picture at the top right of the screen, then choose Profile. Once you access your profile, select Personal Access Tokens in the left-hand menu. Sensitive Property: true This Property is only considered if the [Authentication Method] Property has a value of "Access Token".
E-mail Address	jira-email-address			Your registered e-mail address at Jira Cloud. This Property is only considered if the [Authentication Method] Property has a value of "API Token".
API Token	jira-api-token			Your API token at Jira Cloud. To create such token, visit your Atlassian ID Account Settings page at: https://id.atlassian.com Sensitive Property: true This Property is only considered if the [Authentication Method] Property has a value of "API Token".
Record Reader	record-reader		Controller Service API: RecordReaderFactory Implementations: EBCDICRecordReader JsonTreeReader GrokReader ReaderLookup IPFIXReader WindowsEventLogReader ParquetReader CSVReader Syslog5424Reader JASN1Reader ExcelReader CiscoEmblemSyslogMessageReader ScriptedReader ProtobufReader JsonPathReader XMLReader CEFReader SyslogReader AvroReader YamlTreeReader	Specifies the Controller Service to use for parsing incoming data and determining the data's schema.
Project Key	project-key			The Project Key field is used to uniquely identify a project. This property can either be a constant value, Expression Language or a @{Record Path} format, where the RecordPath is evaluated against each incoming Record. Expression Language is evaluated first. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.
Issue Summary	issue-summary			The summary of the issue. This property can either be a constant value, Expression Language or a @{Record Path} format, where the RecordPath is evaluated against each incoming Record. Expression Language is evaluated first. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.
Issue Description	issue-description			The detailed description of the issue. This property can either be a constant value, Expression Language or a @{Record Path} format, where the RecordPath is evaluated against each incoming Record. Expression Language is evaluated first. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.
Issue Type	issue-type			Issue types categorizes issues, eg. Story, Task, Bug. Issue types can be created in Jira. This property can either be a constant value, Expression Language or a @{Record Path} format, where the RecordPath is evaluated against each incoming Record. Expression Language is evaluated first. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) This Property is only considered if the [Record Reader] Property has a value specified.

Dynamic Properties:

Supports Sensitive Dynamic Properties: No

Dynamic Properties allow the user to specify both the name and value of a property.

Name	Value	Description
An additional attribute to be added to the Jira issue.	The attribute value	User specified Dynamic Properties are added to the Jira issue when a Record Reader is set. The key of the Dynamic Property should be a valid JsonPointer which denotes the JSON path where the extra property is inserted. The value of the property can be plain string, EL or RecordPath and will be inserted as a field value on the given path specified by the property key. In order to provide RecordPath values the @{Record Path Value} notation shall be used. See additional documentation for the Jira issue JSON. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)

Relationships:

Name	Description
success	For FlowFiles created as a result of a successful execution.
failure	For FlowFiles created as a result of an execution error.

Reads Attributes:

None specified.

Writes Attributes:

Name	Description
mime.type	Sets the MIME type to application/json
error.message	The error message returned by PutJiraIssue.
record.count	The number of records processed.
jira.issue.id	The ID of the Jira issue. In case of multiple records corresponds to the ID of the latest response.
jira.issue.key	The key of the Jira issue. In case of multiple records corresponds to the key of the latest response.
jira.issue.self	The link of the canonical location of the issue. In case of multiple records corresponds to the canonical location of the latest response.

State management:

This component does not store state.

Restricted:

This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations: