This processor uses Jira REST API to create a new issue in JIRA. The user may set the basic properties of an issue: the Project Key, the Issue Summary, the Issue Description and the Issue Type. The Project Key can be found in Jira under Project Settings. Issue Types must be created first in Jira before creating a tasks with one. Additional Jira issue attributes can be supplied through Dynamic Properties on the processor.
The Jira server may require the client to authenticate itself, in order to create new issues in Jira. This processor supports authentication through Personal Access Token, in case of Jira Server, and user e-mail & API token, in case of Jira Cloud. The credential must be provided in the same format, as Jira presents it to the user. Providing an invalid token might result in either error messages, or empty responses, depending on the access policy configuration on the server side.
The following properties can be plain strings, EL expressions and RecordPaths. In case of RecordPath evaluation the @{Property Value} format shall be used. First always the Expression Language is evaluated, then the RecordPath.
Additional Dynamic Properties can be defined on the processor in the following format to supply custom Jira attributes:
This is how the basic JSON looks like that the processor sends to JIRA. In case a Record Reader is not set,
this is the expected format of the incoming FlowFile. More examples can be found here
here.
{ "fields": { "project": { "key": "TEST_PROJECT_KEY" }, "summary": "Test summary.", "description": "This is a test issue from PutJiraIssue.", "issuetype": { "name": "Task" } } }
{ "name": "John Doe", "project_id": "DEV", "secret_code": "Batman", "tasks": [ { "title": "Develop PutJiraIssue", "description": "Code day and night until it's done.", "type": "Feature" } ] }
{ "fields": { "project": { "key": "DEV" }, "summary": "Develop PutJiraIssue", "description": "Code day and night until it's done.", "issuetype": { "name": "Feature" }, "extraFields": { "code": "Batman" } } }