Assign issue to user - Glean Help Center

The Jira assign issue action updates the assignee on an existing Jira issue so that agents and workflows can route work to the right owner without manual triage. It operates on a single issue, identified by its issue ID or key, and supports identifying the target user by account ID or assignee name. This write action runs using the connected user’s Jira account and permissions, so it can only assign issues that the user is allowed to view and edit in Jira.

Limitations

Jira actions in Glean are designed for Jira Cloud and do not support Jira Server or Jira Data Center deployments.

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

The underlying toolkit defines the following parameters for Jira Assign issue.

Name	Type	Description
Issue ID or key	String	Identifier of the Jira issue to assign, such as an issue key like ENG-1234.
Account ID	String	Jira account ID of the user who should become the assignee.
Assignee name	String	Human-readable name of the user who should become the assignee.

Usage example

You want to assign a high-priority bug that has been sitting unassigned for too long to the appropriate team owner. Instruction to an agent: “Find the Jira issue ENG-1234 about the API timeout bug and assign it to ABC from the connectors team. ABC is the triage owner for connector issues.” Resulting behavior:

Looks up the Jira issue ENG-1234 to verify it exists and retrieve current details.
Calls the Assign issue action with:
- Issue ID or key set to ENG-1234.
- Assignee name set to ABC (or uses Account ID if the account ID is known).
Updates the issue in Jira so ABC becomes the assignee.
The agent can optionally add a comment or notify ABC about the assignment.

Workflow tip: You can combine this action with Jira search or filter actions to identify unassigned issues, then automatically assign them to the appropriate owners based on labels, components, or priority.

Troubleshooting

Your site admin must authorize this application for the site before the application can access your account

Possible cause: Central OAuth application of Jira is not granted a site-wide access by a Jira administrator.
Fix: Ask your Jira administrator to complete the required app authorization flow in Jira, then retry the action.

Tools return status code 404 or 500 for this tool

Possible cause: The tools server backing this action is unreachable (404) or is 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

Possible cause: The verify_code URI for tools OAuth is not 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 allowed redirect URIs of OAuth application and retry authentication. The tool unique identifier is case-sensitive.

FAQs

How is Jira Assign issue different from Jira Edit issue?

Jira Assign issue focuses on changing who owns an issue, using a small set of parameters related to the assignee. Jira Edit issue is a broader update action that can modify multiple fields on an issue (such as summary, description, assignee, and priority) in a single call. Use Jira Assign issue when you only need to change the owner, and Jira Edit issue when you need to update several fields together.

Agents

​Limitations

​Prerequisites

​Supported parameters

​Usage example

​Troubleshooting