The Jira Get Issue action is used to retrieve the details of a specific issue (task, bug, story, etc.) on Jira. This action allows you to retrieve the summary, description, status, assigned person, date information, and any past updates for the issue. It is ideal for project tracking, bug management, and monitoring work processes.

Technical Specifications

Retrieving Issue Details (Detail Panel): Returns all details of the issue specified by the issue_key parameter and returns them as a JiraIssueResult object.

Parameters:

• settings (Object – required): Contains the settings required for the Jira API connection. The Jira connection defined via Config Manager must be selected.
• issue_key (String – required): The key of the issue in Jira whose details will be retrieved. (e.g., DEV-101)
• update_history (Boolean – optional): If set to true, the issue's change history is also included in the results.

Data Source Compatibility: Parameters can be entered with fixed values or obtained from dynamic sources such as Form Input, Current, Action Result, Method Input via the Symbol Picker.

Web & Mobile Support: The Jira Get Issue action can be used in both web and mobile applications.

Jira Get Issue Application Steps

1. Defining the Action in UI Design

• Open your Kuika project.
• In the UI Design module, select the screen where the issue details will be displayed.
• Add a Button element (e.g., “Show Issue Details”).
• Click on the button and select the + ADD ACTION → Jira → Jira Get Issue action.

2. Configuring Parameters

• settings: Select the Jira API setting you created in Configuration Manager.
• issue_key: Link the issue key selected by the user or specified from the list.
• update_history: If set to true, the issue's past updates are also retrieved.

Usage Scenario: View Issue Details

In a project management application, the user wants to view the details of a specific issue.

Steps:

1. Allow the user to select from the issue list.
2. Add a “Show Details” button.
3. Define the OnClick → Jira Get Issue action.
4. Link the issue_key parameter to the selected issue.
5. Display the returned issue information in the Table element.

Jira Get Issue Advanced Customizations

• History Tracking: You can also display the issue's past changes by using update_history = true.
• Dynamic Usage: Details of different issues can be retrieved dynamically based on user input.
• Result Usage: The returned data can be transferred to other actions (e.g., Jira Update Issue, Jira Delete Issue).
• Status-Based Control: The issue status (e.g., “In Progress,” “Done”) can be retrieved and used for conditional routing in the workflow.

Technical Risks and Controls

• issue_key must not be empty. Otherwise, the operation will fail.
• settings must be configured correctly. If the Jira API setting is not configured in Configuration Manager, the action will not work.
• Authorization checks: If the user does not have permission to view the relevant issue, the operation will fail.
• update_history usage: When this parameter is true, more data may be returned; attention should be paid to performance.