Jira — Other

`simply atlassian jira fields`

List Jira fields, including custom field ids.

Flags

--custom — Only custom fields.
--search <value> — Match against the field name or id, case-insensitively.
--limit <value> — Maximum number of fields to show. (default: 50)

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.

This is what makes —body usable on issue create and update. A custom field is addressed by an id like customfield_10016, which differs between instances and cannot be guessed — so without this command the escape hatch for untyped fields is unusable by anyone who has not read it off an admin screen. —search matches the name or the id, so it answers both “what is Story Points called” and “what is customfield_10016”.

Examples

simply atlassian jira fields --custom

simply atlassian jira fields --search "story points"

simply atlassian jira fields --search customfield_10016 --json

`simply atlassian jira open`

Open a Jira issue or project in the browser.

Flags

--print — Print the URL without opening a browser.

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.

Builds the browser URL for an issue or project and opens it in the default browser. Use —print (or —url) to print the URL without launching a browser.

Examples

simply atlassian jira open PROJ-123

simply atlassian jira open PROJ --print

simply atlassian jira open PROJ-123 --json

`simply atlassian jira project versions`

List a project’s versions.

Flags

--limit <value> — Maximum number of versions to show. (default: 25)

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.

Versions are how Jira models releases. The ID column is what sets fixVersions through —body on issue create or update.

Examples

simply atlassian jira project versions PROJ

simply atlassian jira project versions PROJ --json

`simply atlassian jira projects`

List Jira projects.

Flags

--limit <value> — Maximum number of projects to show. (default: 25)

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 KEY column is the point: it is what every other command takes and what a caller most often does not have. Cloud paginates this endpoint and Server/DC returns the whole list; both are handled.

Examples

simply atlassian jira projects

simply atlassian jira projects --limit 100 --json