# Assignee Rules

You can specify a default assignee for a JIRA ticket by adding the following to your `.nullify.yml` file:

```yaml
integrations:
  jira:
    project_key: EXAMPLE
    [other options]
    assignee:
      id: 123456
      name: John Smith
```

The `name` is the display name of the assignee. The `id` is the user ID of the assignee.

The assignee field is optional. If you do not specify an assignee, or the assignee details provided are invalid, the ticket will still be created but it will be not be assigned to anybody.

You must specify at least one of `id` or `name`.

If both `id` and `name` are specified, the assignee will be set to the user with the specified `id`. If the `id` is set, then the `name` is ignored completely. However, you may still choose to include the `name` if you want to as it might assist your team in identifying the user (it is more readable).

If multiple users have the same `name`, it will assign the ticket to the first user it finds matching that `name`. You can specify the `id` of the user to be more specific.


---

# 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.nullify.ai/connectors/jira/assignee.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.