Issues

Issues

Create, read, update, and delete Jira issues.

Prerequisites

• Authenticated profile (atlcli auth login)
• Jira permission: Browse Projects for read, Edit Issues for write operations

Get Issue

atlcli jira issue get --key PROJ-123

Options:

Flag	Description
--key	Issue key (required)
--expand	Expand: changelog, comments, transitions

Examples

# Get issue with changelog
atlcli jira issue get --key PROJ-123 --expand changelog

# JSON output
atlcli jira issue get --key PROJ-123 --json

Create Issue

atlcli jira issue create --project PROJ --type Task --summary "Fix login bug"

Options:

Flag	Description
--project	Project key (required)
--type	Issue type (required)
--summary	Issue summary (required)
--description	Issue description
--assignee	Assignee account ID
--priority	Priority name
--labels	Comma-separated labels
--parent	Parent issue key (for subtasks)
--field	Set a custom field — <id>=<value>, repeatable

Examples

# Create with full details
atlcli jira issue create --project PROJ --type Bug \
  --summary "Login fails on mobile" \
  --description "Users report 500 error on iOS Safari" \
  --priority High \
  --labels bug,mobile,urgent

# Create and assign
atlcli jira issue create --project PROJ --type Task \
  --summary "Update docs" \
  --assignee 557058:abc123

Adding to Epics or Sprints

Use atlcli jira epic add or atlcli jira sprint add after creating the issue. For templates, use atlcli jira template apply.

Custom Fields

Use --field <id>=<value> to set custom fields when creating or updating issues. The flag can be repeated for multiple fields.

atlcli jira issue create --project PROJ --type Story --summary "My story" \
  --field customfield_10028=5 \
  --field customfield_10077='{"value":"Feature"}' \
  --field customfield_10194="As a user I want to..."

atlcli jira issue update --key PROJ-123 \
  --field customfield_10028=8 \
  --field customfield_10079=3

Value Type Coercion

Values are automatically coerced to the correct type:

Input	Resulting type	Example
Numeric string	number	--field customfield_10028=5
null	null	--field customfield_10028=null
Valid JSON	Parsed value	--field customfield_10077='{"value":"Bug"}'
Everything else	string	--field customfield_10194="Some text"

Use JSON syntax for Jira option, multi-select, and array fields:

# Single select (option)
--field customfield_10077='{"value":"Feature"}'

# Multi-select (array of options)
--field customfield_10195='[{"value":"Goal A"},{"value":"Goal B"}]'

# User field
--field customfield_10050='{"accountId":"557058:abc123"}'

Finding Field IDs

Use atlcli jira field search to look up the ID for a custom field:

atlcli jira field search "story points"
atlcli jira field options customfield_10077   # list allowed option values

Field availability

Custom fields must be on the issue’s create or edit screen in Jira. If you receive a “field cannot be set” error, the field is not configured for that issue type or project screen.

Update Issue

atlcli jira issue update --key PROJ-123 --summary "Updated summary"

Options:

Flag	Description
--key	Issue key (required)
--summary	New summary
--description	New description
--priority	New priority
--add-labels	Add labels (comma-separated)
--remove-labels	Remove labels (comma-separated)
--assignee	New assignee (account ID or none to unassign)
--field	Set a custom field — <id>=<value>, repeatable

Examples

# Update multiple fields
atlcli jira issue update --key PROJ-123 \
  --summary "New summary" \
  --priority Critical

# Modify labels
atlcli jira issue update --key PROJ-123 --add-labels reviewed,verified

# Unassign issue
atlcli jira issue update --key PROJ-123 --assignee none

Delete Issue

atlcli jira issue delete --key PROJ-123 --confirm

Options:

Flag	Description
--key	Issue key (required)
--confirm	Skip confirmation prompt
--delete-subtasks	Also delete subtasks

Transitions

Change issue status:

atlcli jira issue transition --key PROJ-123 --to "In Progress"

Options:

Flag	Description
--key	Issue key (required)
--to	Target status name (required)

List Available Transitions

atlcli jira issue transitions --key PROJ-123

Output:

ID    NAME           TO STATUS
21    Start          In Progress
31    Done           Done
41    Review         In Review

Comments

Add a comment to an issue:

atlcli jira issue comment --key PROJ-123 "Working on this"

The comment text is passed as a positional argument after --key.

Links

# Link issues
atlcli jira issue link --from PROJ-123 --to PROJ-456 --type "blocks"

Options:

Flag	Description
--from	Source issue key (required)
--to	Target issue key (required)
--type	Link type name (required)

Link Types

Common link types:

Type	Description
blocks	This issue blocks another
is blocked by	This issue is blocked by another
duplicates	This issue duplicates another
relates to	General relation
clones	This issue clones another

Watchers

Watcher commands are top-level jira commands:

# List watchers
atlcli jira watchers PROJ-123

# Add yourself as watcher
atlcli jira watch PROJ-123

# Remove yourself
atlcli jira unwatch PROJ-123

Assign

# Assign to user
atlcli jira issue assign --key PROJ-123 --assignee alice@company.com

# Unassign
atlcli jira issue assign --key PROJ-123 --assignee none

Cross-Product Linking

Link Jira issues to Confluence pages for bidirectional traceability.

Link Page to Issue

atlcli jira issue link-page --key PROJ-123 --page 12345

Options:

Flag	Description
--key	Issue key (required)
--page	Confluence page ID (required)

List Linked Pages

atlcli jira issue pages --key PROJ-123

Options:

Flag	Description
--key	Issue key (required)
--space	Filter by Confluence space

Unlink Page

atlcli jira issue unlink-page --key PROJ-123 --page 12345

Examples

# Link a Confluence page to an issue
atlcli jira issue link-page --key PROJ-123 --page 12345

# List all Confluence pages linked to an issue
atlcli jira issue pages --key PROJ-123

# Filter by space
atlcli jira issue pages --key PROJ-123 --space TEAM

# Remove link
atlcli jira issue unlink-page --key PROJ-123 --page 12345

JSON Output

All commands support --json:

atlcli jira issue get --key PROJ-123 --json

{
  "schemaVersion": "1",
  "key": "PROJ-123",
  "id": "10001",
  "summary": "Fix login bug",
  "status": {
    "name": "In Progress",
    "category": "indeterminate"
  },
  "priority": {
    "name": "High",
    "iconUrl": "..."
  },
  "assignee": {
    "displayName": "Alice",
    "emailAddress": "alice@company.com"
  },
  "reporter": {
    "displayName": "Bob",
    "emailAddress": "bob@company.com"
  },
  "created": "2025-01-14T10:00:00Z",
  "updated": "2025-01-14T15:30:00Z",
  "labels": ["bug", "critical"],
  "url": "https://company.atlassian.net/browse/PROJ-123"
}

Related Topics

• Search - Find issues with JQL
• Bulk Operations - Update multiple issues
• Subtasks - Break down issues into subtasks
• Epics - Organize issues into epics