activities
latest
false
UiPath logo, featuring letters U and I in white

Integration Service Activities

Last updated Feb 19, 2026

Get Issue

Project compatibility

Windows | Cross-platform

Overview

Retrieve detailed information of a Jira issue, including assignee, reporter, project, and dynamic fields based on project and issue type

DescriptionAPI MethodAPI PathScopes
Get Jira issue by key/IDGET/rest/api/2/issue/{issueId}
  • read:jira-work - to resolve fields and project/issue-type metadata

Input

ParameterDescriptionData Type
ProjectThe unique key of the project; used to resolve available output fields string
Issue typeThe type of the issue (for example, Task, Story, Bug, Epic, etc.); used to resolve fields string
Issue ID or keyThe issue key (for example, ABCD‑1234) or issue ID string

Output

ParameterDescriptionData Type
IssueThe retrieved issue object object
  • In API workflows, a single response object is returned as the output. Any required fields can be extracted directly from this object.
  • In RPA workflows, some output parameters may differ, but the necessary values can still be retrieved from the response object even if they are not explicitly exposed.

How it works

This activity retrieves an issue in Jira based on the specified issue key and creates a just-in-time (JIT) object that consists of all the related dynamic standard and custom fields.

Once you set the Project and Issue type fields, you can go to Output and see that a JIT object has been created. You can then use the desired fields from the variable's output.

Note: Select the Project and the related Issue type to dynamically retrieve output properties. Once the output properties are set, you can use a variable for the Issue key or ID field. When using variables, you can still use the same output properties during execution, as long as the properties still apply. Alternatively, create a sample Jira project with an issue type that includes all possible fields across various projects and issue types. This enables you to handle different fields in different projects when retrieving the issue.

When using the Get Issue activity that compliments an event trigger from JIRA, you can assign the output of the trigger activity as an input variable in Get Issue. In this case, you are only able to retrieve Get issue response fields for the project the issue belongs to. These issue fields can vary depending on the issue type.

Since issues can have different fields in different projects, we recommend creating a sample Project with an Issue type that contains all possible issue fields across multiple projects and issue types. This ensures that you can create issues across multiple projects and issue types.

Alternatively, you can use the Get Record activity, with an Issues object. However, this scenario prevents us from generating a JIT object for your issue key and you must work with standard fields like Summary, Description, Assignee etc.

  • Project compatibility
  • Overview
  • Input
  • Output
  • How it works

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2026 UiPath. All rights reserved.