Skip to main content
The cops release projects commands let you manage the project configurations stored in cops.project.json. These commands are local operations — they read and write the config file and do not call any Atlassian APIs.

cops release projects list

List all projects configured in cops.project.json.Alias: cops release projects ls

Usage

cops release projects list [flags]

Flags

--output
string
default:"table"
Output format: table, json, or markdown.

Output columns

project, default, source
ColumnDescription
projectProject key
defaulttrue when this is the default project
sourceConfig source: projects (multi-project map) or release (legacy top-level config)

Examples

cops release projects list
project     default  source
──────────  ───────  ────────
my-service  true     projects
auth-lib    false    projects
Show the resolved release configuration for a project. Displays all connection details and the number of configured gates.

Usage

cops release projects show [--project <key>] [flags]

Flags

--project
string
Project key from the projects map. Defaults to defaultProject or the top-level release block.
--output
string
default:"table"
Output format: table, json, or markdown.

Output columns

project, jiraProjectKey, jiraFixVersion, confluenceSpace, confluenceTitle, bitbucketProjectKey, bitbucketRepo, releaseBranch, bambooPlan, gateCount

Examples

cops release projects show
project     jiraProjectKey  jiraFixVersion  confluenceSpace  bitbucketRepo  releaseBranch    bambooPlan  gateCount
──────────  ──────────────  ──────────────  ───────────────  ─────────────  ───────────────  ──────────  ─────────
my-service  MYPROJ          2026-Q1         RELEASE          my-service     release/2026-Q1  PROJ-PLAN   5
Migrate a legacy cops.project.json (with a top-level release block) to the projects/defaultProject format. The migration wraps the existing release block under projects.<projectId> and sets defaultProject.

Usage

cops release projects migrate [flags]

Flags

--projectId
string
default:"default"
Project ID to assign to the migrated legacy release configuration.
--dryRun
boolean
default:"false"
Preview the migration without writing any changes to disk.
--backup
boolean
default:"false"
Create a backup of cops.project.json at cops.project.json.bak before writing the migrated config.
--output
string
default:"table"
Output format: table, json, or markdown.

Output columns

file, changed, dryRun, backupCreated, backupPath, details

Exit codes

CodeMeaning
0No migration was needed (config is already in projects format)
2Migration was applied (changed)

Examples

cops release projects migrate --dryRun
This command overwrites cops.project.json in the current working directory. Use --dryRun to preview changes before applying, and --backup to keep a copy of the original.

cops release check

Run release gates for a configured project.

cops release summary

Cross-product release readiness summary.

Build docs developers (and LLMs) love