The Jira Get Issues action is used to list multiple issues on Jira according to specific criteria. This action allows you to perform bulk issue queries using JQL queries, project filters, or limit values. It is particularly useful for project management, reporting, backlog viewing, and workload analysis.

Technical Specifications

Bulk Issue Retrieval (List Panel): Returns multiple issue details based on the given parameters and sends them back as JiraIssueDto (Many) objects.

Parameters:

• settings (Object – required): Contains the settings required for the Jira API connection. The Jira connection defined via Config Manager must be selected.
• jql (String – optional): Issues can be filtered using Jira Query Language (JQL) expressions. (e.g., status = “In Progress” AND assignee = currentUser())
• limit (Int32 – optional): Maximum number of issues to return. (e.g., 50)
• start_at (Int32 – optional): The starting index for listing (used for pagination).
• projects_filter (String – optional): Used to filter issues by a specific project (e.g., DEV, QA).

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

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

Jira Get Issues Application Steps

1. Defining the Action in UI Design

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

2. Configuring Parameters

• settings: Select the Jira API setting you created in Configuration Manager.
• jql: Write a query as needed (e.g., project = DEV AND status != Done).
• limit: Specify the maximum number of issues to return.
• start_at: Enter the starting index for pagination.
• projects_filter: The list can be filtered by entering a specific project key.

Use Case: Listing the Backlog

In a project management application, the user wants to see a list of open tasks in the “DEV” project.

Steps:

1. Add a “Show Tasks” button.
2. OnClick → Connect the Jira Get Issues action.
3. Write project = DEV AND status != Done in the jql parameter.
4. Display the returned results in the Table element.

Jira Get Issues Advanced Customizations

• Dynamic Filtering: You can dynamically create a JQL query by letting the user select status, priority, or assignee.
• Pagination: Pagination can be implemented with the limit and start_at parameters when there are too many issues.
• Project-Based Reporting: Reporting based on multiple projects can be implemented using the projects_filter parameter.
• Using the Result: The returned issue list can be transferred to other actions (e.g., Jira Update Issue, Jira Delete Issue).

Technical Risks and Controls

• settings must be configured correctly. If the Jira API setting is not configured in Configuration Manager, the action will not work.
• If jql is written incorrectly, Jira will return an error.
• limit should not be too high. Calling too many issues can cause performance issues.
• Permission restrictions: If the user does not have permission to view projects or issues, the results may be incomplete.