Create an issue in Jira
Creates an issue in Jira.
Application
- Jira
Inputs (what you have)
| Name | Description | Data Type | Required? | Example |
|---|---|---|---|---|
| Project | The project the issue will be created in | Text(short) | Yes | |
| Issue type | The type of the issue (Task, Bug, Feature, Improvement, etc.) | Text(short) | Yes | |
| Issue summary | The summary or title of the issue | Text(Long) | Yes | |
| Issue description | The detailed description of the issue | Text(Long) | No | |
| Status | The status of the issue (Backlog, In Progress, Done, etc.) | Text(short) | No | |
| Priority | The priority of the issue (P1, P2, P3, etc.) | Text(short) | No | |
| Assignee | The email of the person assigned to the issue | No | ||
| Reporter | The email of the person who reported the issue | No | ||
| Labels | A list of labels for the ticket | List of Text | No | |
| Parent issue link | If creating a subtask, the parent issue link of the task to create the sub-tsk under | URL | No |
Review the authentication methods requirements below.
Note: the value of inputs can either be a set value in the configuration of the Wrk Action within the Wrkflow, or a variable from the Data library section. These variables in the Data library section are the outputs of previous Wrk Actions in the Wrkflow.
Outputs (what you get)
| Name | Description | Data Type | Required | Example |
|---|---|---|---|---|
| Jira issue link | Link to the Jira issue | URL | Yes | https://your-domain.atlassian.net/browse/PROJ-123 |
Outcomes
| Name | Description |
|---|---|
| Success | This status is selected in the event the Wrk Action successfully returns the details from the Jira issue |
| No Result | This status is selected in the event of the following scenarios:Unable to find any issues with the provided link |
| Impossible To Complete | This status is selected in the event of the following scenarios:Any of the provided inputs are not validThe external system is not accessibleUnable to access with the provided credentialsUnable to perform the requested task with the provided credentialsMultiple sites exist but no site was specifiedThe specified site does not exist |
Requirements
Authentication Method(s)
Connected Accounts will need to use the provided access token in order to find out the “cloudid” of the Jira site our user is connecting from. This will be used as part of all Jira API calls.
Inputs:
| Title | Data Type | Required/Optional | Description |
|---|---|---|---|
| Jira connected account | Connected Account | Required | |
| Jira site link | url | Optional | If you use multiple Jira sites specify the site you would like to connect to. e.g. https://CompanyName.atlassian.net |