Retrieve issue details from Jira
Retrieves the details of an existing Jira issue. Use the fields to capture section to retrieve custom field details by entering the name of the Jira field as your WA field name. Replace special characters in Jira field names with underscores when using fields to capture.
Application
- Jira
Inputs (what you have)
| Name | Description | Data Type | Required? | Example |
|---|---|---|---|---|
| Jira issue link | Link to the Jira issue | URL | Yes | https://your-domain.atlassian.net/browse/PROJ-123 |
| Fields to Capture | N/A |
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 |
|---|---|---|---|---|
| Issue key | The unique identifier of the issue returned | 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) | Yes | |
| Issue type | The type of the issue (Task, Bug, Feature, Improvment, etc.) | Text(short) | Yes | |
| Status | The status of the issue (Backlog, In Progress, Done, etc.) | Text(short) | Yes | |
| Priority | The priority of the issue (P1, P2, P3, etc.) | Text(short) | Yes | |
| Assignee | The email of the person assigned to the issue | Yes | ||
| Reporter | The email of the person who reported the issue | Yes | ||
| Creator | The email of the person who created the issue | Yes | ||
| Created At | The date and time that the issue was created | Date Time | Yes | |
| Updated At | The date and time that the issue was last updated | Date Time | Yes | |
| Resolution | If done, the resolution of the issue (Done, Won’t Do, Duplicate, etc.) | Text(short) | Yes | |
| Project | The project the issue was created in | Text(short) | Yes | |
| Labels | A list of labels for the ticket | List of Text | Yes | |
| Watchers | List of users emails who are watching the issue. | List of Email | Yes | |
| Sub-task links | List of Jira links for the sub-tasks associated with this issue | List of URLs | Yes | |
| Has attachments? | A true or false indication of whether or not the issue has attachments | True or False | Yes | |
| Has comments? | A true or false indication of whether or not the issue has comments | True or False | Yes | |
| Story points | If using Agile/Scrum, this field often represents the estimated effort required to complete the story. | Integer | Yes | |
| Epic link | If using the Agile/Scrum process, this links a story to an epic. | URLs | Yes | |
| Custom Fields | Specified using fields to capture | No |
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:The ‘Jira issue link’ provided is not in the correct formatThe 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 |