# Issue :: Set assignment directly

## Summary

Sets an assignee on the JIRA issue with an assignee string using the asynchronous request queue. Retries are automatically handled.

## Action Inputs

| Label                | Name                   | Type                                  | Mandatory | Description                                                                                                                                                                                                                 |
| -------------------- | ---------------------- | ------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Connector            | connector              | Reference (Reference: Jira Connector) | No        | \[optional] The sys\_id of the connector to use in the process. If this is blank, the default connector is used.                                                                                                            |
| Issue ID or Key      | issue\_id\_or\_key     | String                                | No        | The JIRA issue ID or Key of the issue to retrieve (This is only used if 'linkage' is not set)                                                                                                                               |
| Assignee String      | assignee\_string       | String                                | No        | The value that will be set as the assignee on the JIRA issue. This will need to match a username in JIRA or be an Account ID of a user in JIRA. Modern JIRA versions require this to be an account ID instead of a username |
| Execute ASAP         | execute\_asap          | True/False                            | No        | Whether to run this as an asynchronous business rule when the record gets created or wait for the job to pick it up in relative order on the queue. It is recommended to leave this unchecked.                              |
| Assignee String Type | assignee\_string\_type | Choice                                | No        | Whether the assignee string is a username or an account ID                                                                                                                                                                  |

## Action Outputs

| Label         | Name           | Type                                       | Mandatory | Description                                                                                 |
| ------------- | -------------- | ------------------------------------------ | --------- | ------------------------------------------------------------------------------------------- |
| Request       | request        | Reference (Reference: Async Request Queue) | No        | The original asynchronous request queue record used to make the request                     |
| Success       | success        | True/False                                 | No        | Whether the communication and response was as expected                                      |
| Log           | log            | String                                     | No        | Scripted log statements of activities that took place during the operation of this activity |
| Retry Request | retry\_request | Reference (Reference: Async Request Queue) | No        | If there were Retries used in the process, the last retry record is returned                |
| Response JSON | string         | String                                     | No        | The string returned from the API call                                                       |

## Notes

* This action belongs to the **JIRA Request Queue** category.
* This action includes reference fields that link to other tables in ServiceNow:
  * references the table.
* This action returns 5 output(s) that can be used in subsequent flow steps.

## Example Usage

### Example 1: Basic Usage

This example demonstrates how to use the action with typical inputs.

**Input:**

**Output:**

In this example, the action processes the provided inputs and returns the appropriate outputs. The actual values returned will depend on the specific functionality of this action and the input values provided.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.yansalabs.com/jira-integration-framework/technical-docs/spoke-actions/issue-set-assignment-directly.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.