Skip to content
Simply SF logoSimply SF logoSimply CLI

Jira — Users

Section titled “simply atlassian jira user search”

Find users by name or email.

Flags

  • --limit <value> — Maximum number of users to return. (default: 20)

Connection

  • -e, --env-file <value> — Path to a .env file holding connection settings.
  • --jira-url <value> — Base URL of the Jira instance. (env: JIRA_URL)
  • --jira-username <value> — Account email for Jira Cloud basic auth. (env: JIRA_USERNAME)
  • --jira-api-token <value> — API token for Jira Cloud basic auth. (env: JIRA_API_TOKEN)
  • --jira-personal-token <value> — Personal access token for Jira Server/Data Center. (env: JIRA_PERSONAL_TOKEN)

Global

  • --json — the raw API payload, for scripts and agents.

The account id column is the point of this command: it is what —mention and —assignee need, and it is not something anyone can guess. On Cloud, whether an email address is visible is a per-user privacy setting, so that column is often empty — searching by an email address still works even when it is not shown back.

This adds no access the credential does not already have, but it does put colleagues’ names and addresses wherever the output goes. When an AI agent is the caller, that means into its context — worth a thought before running it broadly against a work instance.

Examples

Terminal window
simply atlassian jira user search ada
Terminal window
simply atlassian jira user search ada@example.com
Terminal window
simply atlassian jira user search ada --json

simply atlassian jira user view

Section titled “simply atlassian jira user view”

Show one user.

Connection

  • -e, --env-file <value> — Path to a .env file holding connection settings.
  • --jira-url <value> — Base URL of the Jira instance. (env: JIRA_URL)
  • --jira-username <value> — Account email for Jira Cloud basic auth. (env: JIRA_USERNAME)
  • --jira-api-token <value> — API token for Jira Cloud basic auth. (env: JIRA_API_TOKEN)
  • --jira-personal-token <value> — Personal access token for Jira Server/Data Center. (env: JIRA_PERSONAL_TOKEN)

Global

  • --json — the raw API payload, for scripts and agents.

Takes an account id on Cloud, or a username on Server/Data Center — the same distinction the connection settings make. Use “user search” if you have a name rather than an id.

Examples

Terminal window
simply atlassian jira user view 70121:8d8e579e-980f-49ed-93ec-0a0d519f60e4
Terminal window
simply atlassian jira user view ada --json

simply atlassian jira whoami

Section titled “simply atlassian jira whoami”

Show the account the configured credentials belong to.

Connection

  • -e, --env-file <value> — Path to a .env file holding connection settings.
  • --jira-url <value> — Base URL of the Jira instance. (env: JIRA_URL)
  • --jira-username <value> — Account email for Jira Cloud basic auth. (env: JIRA_USERNAME)
  • --jira-api-token <value> — API token for Jira Cloud basic auth. (env: JIRA_API_TOKEN)
  • --jira-personal-token <value> — Personal access token for Jira Server/Data Center. (env: JIRA_PERSONAL_TOKEN)

Global

  • --json — the raw API payload, for scripts and agents.

Calls the Jira /myself endpoint. This is the cheapest way to confirm that the URL, credentials, and network path all work before running anything heavier.

Examples

Terminal window
simply atlassian jira whoami
Terminal window
simply atlassian jira whoami --env-file .env
Terminal window
simply atlassian jira whoami --json