Limitations
- Jira actions are designed for Jira Cloud and do not support Jira Server or Data Center deployments.
- If your Jira administrator has not granted site-wide access to the Jira OAuth app, users may see an error that the site admin must authorize the app before it can access their account.
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 must connect their Jira account via OAuth in Glean before running agents that use Jira actions, including Jira Get issue.
- If your Jira organization uses Central OAuth, a Jira administrator must authorize the app for the site before users can run Jira actions.
Supported parameters
The underlying action defines the following parameters for Jira Get issue.| Name | Type | Description |
|---|---|---|
| Issue ID or key | String | Identifier of the Jira issue to retrieve, such as an issue key like EE-1234 or the internal issue ID. |
| Expand | String | Optional comma-separated list of expansion options passed through to Jira’s issue API for advanced use cases. |
| Fields | String or list | Optional set of Jira field identifiers to request from the REST API when you want to narrow or customize the returned fields. |
| Fields by keys | Boolean | Optional flag that controls how Jira interprets the fields parameter; see Jira REST API documentation for supported behavior. |
| Properties | String or list | Optional list of Jira issue property keys to include in the response, passed through to the underlying Jira API. |
| Update history | Boolean | Optional flag corresponding to Jira’s updateHistory behavior; confirm the desired value based on your Jira REST API configuration. |
Usage example
You want to review a high-priority bug that has been open for several weeks to determine if it needs attention or re-prioritization. Instruction to an agent: “Look up Jira issue ENG-567 and tell me: what is the current status, who is assigned to it, when was it last updated, and what is the priority level? Also, summarize the issue description.” Resulting behavior:-
Calls the Get issue action with:
Issue ID or keyset to ENG-567.
- Retrieves the complete issue details including all standard fields.
-
Returns structured information about:
- Status: In Progress
- Assignee: ABC
- Last updated: November 15, 2024
- Priority: High
- Description summary: API timeout occurring when users make batch requests.
- The agent can then combine this with other data sources or use it to decide on follow-up actions like adding comments or updating fields.
Troubleshooting
Your site admin must authorize this application for the site before the application can access your account
Your site admin must authorize this application for the site before the application can access your account
Tools return status code 404 or 500 for this tool
Tools return status code 404 or 500 for this tool
- Possible cause: The tools server backing this action is unreachable (404) or returning an internal error (500).
- Fix: Confirm that the server information of the action is correct and reachable from Glean. For 500 errors, the tool creator needs to fix the server or 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 must add https://your-glean-instance-be.glean.com/tools/oauth/verify_code/toolUniqueIdentifier to the allowed redirect URIs of OAuth application and retry authentication. The tool unique identifier is case-sensitive.
FAQs
How is Jira Get issue different from Search Jira with JQL?
How is Jira Get issue different from Search Jira with JQL?
Jira Get issue targets a single issue by ID or key, while Search Jira with JQL runs a JQL query and can return many matching issues up to the configured limits of the search action.