The Jira Get User action retrieves detailed information about a specific user in Jira. Queries can be made using the user_identifier parameter via username, email, or account ID.

Technical Specifications

Retrieve User Information: Detailed information about the specified user is returned. The returned data type is JiraUserInfoResult (One).

Parameters:

• settings (Object – required): Contains Jira connection settings. The Jira API setting defined via Config Manager must be selected.
• user_identifier (String – required): The value that identifies the user. In Jira, this field can be accountId, username, or email (accountId is usually preferred for Jira Cloud).

Data Source Compatibility:

• A fixed value (Fixed Value) can be entered.
• It can be obtained from dynamic sources (Form Input, Current, Action Result, Method Input).

Web & Mobile Support: Can be used in web and mobile applications.

Jira Get User Application Steps

1. Adding an Action in UI Design

• Go to the screen where you want to get user information.
• Add a Button element (e.g., “Get User Information”).
• Click on the button → + ADD ACTION → Jira → Jira Get User.

2. Defining Parameters

• settings: Select your Jira connection from the Configuration Manager.
• user_identifier: Enter the user's accountId, email address, or username in Jira, or link it dynamically.

3. Using the Returned Data

• The returned result is of type JiraUserInfoResult. It contains information such as displayName, emailAddress, accountId, active, and timeZone.
• You can link this data to a Text, Profile Card, or User Detail Component.

Usage Scenario: Viewing the User Profile

An administrator wants to view the information of the user with the Jira address mary.watson@company.com.

Steps:

1. Click the “Show User Profile” button.
2. The Jira Get User action is triggered.
3. The returned user information (First Name, Last Name, Email, Active/Inactive, TimeZone) is displayed on the screen.

Jira Get User Action Advanced Customizations

• Dynamic User Identifier: The accountId of the person selected in the user list can be sent as a parameter to this action.
• Role-Based Usage: The returned user information can be linked as a parameter to other actions (e.g., Jira Assign Issue).
• Combination: First, the user is searched for with the Jira Search Users → Jira Get User chain, then the details are retrieved.

Technical Risks and Controls

• The correct Identifier must be used. In Jira Cloud, accountId is usually required; in older versions, username or email may be supported.
• Settings must be configured correctly. Otherwise, user information cannot be retrieved.
• There may be permission restrictions. Some user information may not be returned due to privacy settings.