# Get Atlassian User ID

Look up the Atlassian account ID for a person from a runbook

Resolves a person to their Atlassian account ID. Jira's own APIs identify people by account ID, not by email address, so this is the lookup that lets a runbook hand a person to another Jira step.

The tool is read-only. It never creates a Jira user or a Jira Service Management customer.

## How It Works

1. The agent gives the tool one **identifier**: an email address or a Risotto identity ID.
2. Risotto checks the Atlassian identities it already holds for that person. Risotto records one whenever it sees a Jira user, so a known person resolves without calling Jira.
3. When nothing is recorded, the tool searches Jira for the email address. Jira's user search matches loosely across names and email addresses, so only an exact email match is accepted.
4. A match found this way is recorded, so later lookups for the same person resolve locally.

The tool returns JSON with `account_id`, `email`, `source`, and `error`. `account_id` is `null` and `error` says why when no matching account exists, so a script or a later step can read the reason.

## Authentication

This tool runs on your organization's Jira connection, the same connection the ticket sync uses. There are no credentials to enter on the tool itself.

Connect Jira under **Settings → Integrations** first. See the [Jira integration](https://www.tryrisotto.com/docs/integrations/ticketing/jira) guide.

> **Note:** The tool uses the current Jira app (Forge). An organization still on the older
> Atlassian Connect app gets "Jira is not connected for this organization." See
> [Migrate from Connect to
> Forge](https://www.tryrisotto.com/docs/integrations/ticketing/migrate-connect-to-forge).

## Configuration Options

None. The tool takes its connection from the organization.

## Example Runbook Uses

- Resolve the requestor before a step that needs an account ID, such as [Add Participant to Work Item](https://www.tryrisotto.com/docs/integrations/tools/jira/add_participant_to_work_item)
- Confirm a new hire has a Jira account before the onboarding runbook assigns them work
- Check whether a contractor named in a request exists in Jira at all

## Limitations

- The lookup matches on the email address only. A person whose Jira account carries a different address does not resolve.
- Portal-only Jira Service Management customers do not appear in Jira's user search, so they do not resolve here.
- A Jira account with a hidden email address resolves only when Risotto can read the address through the Jira app.

## Troubleshooting

### No Atlassian account with the email address was found

The address does not match a Jira account exactly. Check the address on the
person's Jira profile, and remember that a portal-only customer is not
returned by user search.

### Jira is not connected for this organization

Install the Jira app under **Settings → Integrations**. An organization on the
older Connect app must migrate first.

### The Risotto identity has no known email address

The identity ID the agent passed belongs to a person with no email address
on record. Pass the email address directly instead.

## Related

- [Add Participant to Work Item](https://www.tryrisotto.com/docs/integrations/tools/jira/add_participant_to_work_item)
- [Jira integration](https://www.tryrisotto.com/docs/integrations/ticketing/jira)

Source: https://www.tryrisotto.com/docs/integrations/tools/jira/get_atlassian_user_id
