Projects
Projects
Section titled “Projects”View and manage Jira projects.
Prerequisites
Section titled “Prerequisites”- Authenticated profile (
atlcli auth login) - Jira permission: Browse Projects (read), Administer Projects (create/update)
List Projects
Section titled “List Projects”View all accessible projects:
atlcli jira project listOutput:
KEY NAME LEAD TYPEPROJ Main Project alice@company SoftwareSUPPORT Customer Support bob@company Service DeskINFRA Infrastructure carol@company SoftwareOptions:
| Flag | Description |
|---|---|
--type | Filter by project type |
--limit | Maximum results |
--json | JSON output |
Filter Projects
Section titled “Filter Projects”# Software projects onlyatlcli jira project list --type software
# Search by nameatlcli jira project list --json | jq '.projects[] | select(.name | contains("Support"))'Get Project Details
Section titled “Get Project Details”View details of a specific project:
atlcli jira project get PROJOutput:
Key: PROJName: Main ProjectLead: Alice (alice@company.com)Type: SoftwareURL: https://company.atlassian.net/browse/PROJDescription: Main product development project
Issue Types: - Story - Task - Bug - Epic - Sub-task
Components: - Backend (lead: bob@company.com) - Frontend (lead: carol@company.com) - API (lead: alice@company.com)Options:
| Flag | Description |
|---|---|
--expand | Include additional data: components, versions, issueTypes |
Project Issue Types
Section titled “Project Issue Types”List available issue types for a project:
atlcli jira project types PROJOutput:
ID NAME SUBTASK DESCRIPTION10001 Story No User story for feature work10002 Task No General task10003 Bug No Software defect10004 Epic No Large feature or initiative10005 Sub-task Yes Subtask of another issueThis is useful when creating issues to know which types are available.
Components
Section titled “Components”List Components
Section titled “List Components”atlcli jira component list --project PROJOutput:
ID NAME LEAD ISSUES10100 Backend bob@company 4510101 Frontend carol@company 3210102 API alice@company 28Create Component
Section titled “Create Component”atlcli jira component create --project PROJ --name "Mobile" --lead dave@company.comOptions:
| Flag | Description |
|---|---|
--project | Project key (required) |
--name | Component name (required) |
--lead | Component lead email |
--description | Component description |
Update Component
Section titled “Update Component”atlcli jira component update 10100 --name "Backend API" --lead alice@company.comDelete Component
Section titled “Delete Component”atlcli jira component delete 10100 --confirmOptions:
| Flag | Description |
|---|---|
--move-to | Move issues to another component |
--confirm | Skip confirmation |
Versions
Section titled “Versions”List Versions
Section titled “List Versions”atlcli jira version list --project PROJOutput:
ID NAME STATUS RELEASE DATE ISSUES10200 v1.0 Released 2024-12-01 4510201 v1.1 Released 2025-01-01 3210202 v2.0 Unreleased 2025-03-01 28Create Version
Section titled “Create Version”atlcli jira version create --project PROJ --name "v2.1" --release-date 2025-06-01Options:
| Flag | Description |
|---|---|
--project | Project key (required) |
--name | Version name (required) |
--description | Version description |
--release-date | Planned release date |
--start-date | Development start date |
Release Version
Section titled “Release Version”Mark a version as released:
atlcli jira version release 10202Options:
| Flag | Description |
|---|---|
--release-date | Actual release date (defaults to today) |
--move-unfixed | Move unfixed issues to another version |
Update Version
Section titled “Update Version”atlcli jira version update 10202 --name "v2.0.0" --release-date 2025-04-01Delete Version
Section titled “Delete Version”atlcli jira version delete 10202 --confirmOptions:
| Flag | Description |
|---|---|
--move-fix | Move fix version issues to another version |
--move-affects | Move affects version issues to another version |
--confirm | Skip confirmation |
JSON Output
Section titled “JSON Output”atlcli jira project get PROJ --json{ "schemaVersion": "1", "project": { "id": "10000", "key": "PROJ", "name": "Main Project", "projectTypeKey": "software", "lead": { "displayName": "Alice", "email": "alice@company.com" }, "url": "https://company.atlassian.net/browse/PROJ", "issueTypes": [ {"id": "10001", "name": "Story", "subtask": false}, {"id": "10002", "name": "Task", "subtask": false}, {"id": "10005", "name": "Sub-task", "subtask": true} ], "components": [ {"id": "10100", "name": "Backend", "lead": "bob@company.com"} ], "versions": [ {"id": "10200", "name": "v1.0", "released": true} ] }}Use Cases
Section titled “Use Cases”Project Overview Script
Section titled “Project Overview Script”# Get summary of all projectsatlcli jira project list --json | jq -r '.projects[] | "\(.key): \(.name) (\(.projectTypeKey))"'Find Available Issue Types
Section titled “Find Available Issue Types”# Before creating an issue, check available typesatlcli jira project types PROJ --json | jq -r '.issueTypes[] | select(.subtask == false) | .name'Release Management
Section titled “Release Management”# Release a version and move incomplete issuesatlcli jira version release 10202 --move-unfixed 10203
# Create next versionatlcli jira version create --project PROJ --name "v2.1" --start-date $(date +%Y-%m-%d)Component Statistics
Section titled “Component Statistics”# Issues per componentatlcli jira component list --project PROJ --json | \ jq -r '.components[] | "\(.name): \(.issueCount) issues"'Related Topics
Section titled “Related Topics”- Issues - Work with issues in projects
- Fields - Custom fields per project
- Boards & Sprints - Boards associated with projects
Jira and Confluence are trademarks of Atlassian Corporation Plc.
atlcli is not affiliated with, endorsed by, or sponsored by Atlassian.