Skip to content
Simply SF logoSimply SF logoSimply CLI

Jira — Issue links

Section titled “simply atlassian jira issue link create”

Link two Jira issues.

Flags

  • --dry-run — Print the request that would be sent and exit without sending it.
  • --comment <value> — Comment to add to the link.

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 relationship is given the way it would be said out loud: “A blocks B”. Either direction of a type works — “A blocks B” and “B is blocked by A” state the same fact and produce the same link — so the phrasing can follow whatever the source text used. The type may also be given by name, which is read as its outward phrase. An unmatched type lists what the instance offers. Use “issue link types” to see them, or —dry-run to check without sending.

Examples

Terminal window
simply atlassian jira issue link create PROJ-1 blocks PROJ-2
Terminal window
simply atlassian jira issue link create PROJ-2 "is blocked by" PROJ-1
Terminal window
simply atlassian jira issue link create PROJ-1 relates PROJ-3 --comment "same root cause"
Section titled “simply atlassian jira issue link delete”

Delete an issue link.

Flags

  • --dry-run — Print the request that would be sent and exit without sending it.

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 the link id, which “issue link list” prints. The link is resolved first, so both the dry run and the result name the relationship being removed rather than only its id — a link id is instance-global and identifies nothing on its own. Unlike issue and comment deletion this does not require —confirm: what it prints is enough to re-create the link in one command, so it is not the irreversible loss of data that —confirm exists to guard.

Examples

Terminal window
simply atlassian jira issue link delete 10201
Terminal window
simply atlassian jira issue link delete 10201 --dry-run
Section titled “simply atlassian jira issue link list”

List an issue’s links.

Flags

  • --limit <value> — Maximum number of links 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.

Each relationship is phrased from the perspective of the issue asked about, so “blocks” means this issue blocks the one named. The ID column is what “issue link delete” needs and is not otherwise discoverable.

Examples

Terminal window
simply atlassian jira issue link list PROJ-123
Terminal window
simply atlassian jira issue link list PROJ-123 --json
Section titled “simply atlassian jira issue link types”

List the issue link types this instance offers.

Flags

  • --limit <value> — Maximum number of link types 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.

Both phrases are shown because either one can be passed to “issue link create”, and neither is guessable from the type name — Duplicate offers “duplicates” and “is duplicated by”. Link types are configured per instance, so this list is the authority.

Examples

Terminal window
simply atlassian jira issue link types
Terminal window
simply atlassian jira issue link types --json