The Jira Get Project Issues action allows you to list issues belonging to a specific project in Jira in bulk. It returns all tasks in the project selected via the project_key parameter. It is particularly useful in project-based backlog, sprint planning, or reporting scenarios.

Technical Specifications

Bulk Issue Retrieval (Project-Based): Returns all issues in the selected project. The return type is JiraIssueDto (Many).

Parameters:

• settings (Object – required): Contains Jira connection settings. The Jira setting defined via Config Manager must be selected.
• project_key (String – required): The key code of the Jira project (e.g., DEV, QA, OPS).
• limit (Int32 – optional): The maximum number of issues to return (e.g., 50).
• start_at (Int32 – optional): The starting index value for pagination.

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

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

Jira Get Project Issues Application Steps

1. Adding an Action in UI Design

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

2. Defining Parameters

• settings: Select your Jira API settings from Configuration Manager.
• project_key: Enter the project key (e.g., DEV).
• limit: Specify the maximum number of issues.
• start_at: Enter the start index (for pagination).

Use Case: Viewing Project-Based Backlog

An administrator wants to list all open issues in the “QA” project.

Steps:

1. Add the “Show QA Project Tasks” button.
2. OnClick → Connect the Jira Get Project Issues action.
3. Enter QA in the project_key field.
4. Connect the returned results to the Table element.

Jira Get Project Issues Advanced Customizations

• Dynamic Project Key: You can let the user select a project and connect the selected value to the project_key parameter.
• Pagination Support: When there are many issues, you can paginate using the limit and start_at parameters.
• Listing + Action: Instead of just viewing the returned issues, you can chain the Jira Get Issue or Jira Update Issue actions on the selected issue.

Technical Risks and Controls

• project_key must be entered correctly. An incorrect or non-existent project key returns an error.
• settings must be configured correctly. It will not work if the Jira API connection is not made in the Configuration Manager.
• The limit should not be too large. High values may negatively affect performance.
• There may be permission restrictions. If the user does not have permission to view issues in the relevant project, the results may be incomplete.