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". |
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) |
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) |
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) |
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) |
Cache Size | cache-size | 1000 | | Specifies how many Jira tasks should be cached. |
Cache Expiration | cache-expiration | 1 hour | | Specifies how long a Jira task that is cached should remain in the cache. |
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. 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) |
State management:
This component does not store state.Restricted:
This component is not restricted.System Resource Considerations:
None specified.