Prerequisites
- Your admin must complete the initial Jira setup and enable Jira actions in the Admin Console so that the Jira action pack is available in Agent Builder.
- Each user is prompted to connect their Jira account via OAuth in Glean before running agents that use Jira actions, including Jira Assign issue.
- If your Jira organization uses Central OAuth, a Jira administrator must authorize the app for the site before users can run Jira actions in Glean.
Supported parameters
| Parameter | Type | Description |
|---|---|---|
| Max results | Integer | Maximum number of users to return in a single call. |
| Start at | Integer | Starting position in the overall user list for pagination. |
Usage examples
- “Get all Jira users from our instance so I can generate a report for the quarterly audit.”
- “List all user accounts in our Jira Cloud.”
- “Show me all active and inactive users in Jira.”
Troubleshooting
Site admin must authorize this app for the site
Site admin must authorize this app for the site
No users returned or fewer users than expected
No users returned or fewer users than expected
- Possible cause: The connected account does not have permission to view user information, or pagination parameters are incorrect.
- Fix: Verify the connected account has permission to view users in Jira. Check that Start at is not beyond the total number of users.
Tools backend returned status code 404 or 500
Tools backend returned status code 404 or 500
- Possible cause: The tools server backing this action is unreachable (404) or returning an internal error (500).
- Fix: Confirm that the server information of teh action is correct and reachable from Glean. For 500 errors, contact Glean support to investigate the underlying exception.
Invalid redirect URI during Jira authentication
Invalid redirect URI during Jira authentication
- Possible cause: The verify_code URI for tools OAuth has not been added to the allowed redirect URIs for the Jira OAuth app.
- Fix: An admin should add https://your-glean-instance-be.glean.com/tools/oauth/verify_code/toolUniqueIdentifier to the OAuth app’s allowed redirect URIs and retry authentication.
FAQs
Does Get all users work with Jira Server or Data Center?
Does Get all users work with Jira Server or Data Center?
No. Jira actions in Glean are designed for Jira Cloud and rely on Jira Cloud’s REST APIs and OAuth-based integration. They do not support Jira Server or Data Center deployments.
Whose permissions does the action use when retrieving users?
Whose permissions does the action use when retrieving users?
The action runs using the connected Jira account for the current user, so it can only return information that this Jira account is allowed to access in Jira.
Can I use this action to search for a specific user?
Can I use this action to search for a specific user?
No. Get all users is designed to list all users with pagination, not to search for specific users. To search for users by name, email, or account ID, use Find users instead.
How does pagination work?
How does pagination work?
Use Results limit to control how many users are returned per page, and Start at to specify the starting index. For example, to get the second page of 100 users, set Start at to 100 and Results limit to 100.
Does this action include inactive users?
Does this action include inactive users?
Yes. Get all users returns all users in the Jira instance, including both active and inactive users. The user status information is included in the response.