Skip to main content
cops release summary produces a cross-product readiness report for a release. When cops.project.json contains configured gates, the command evaluates those gates directly (same logic as cops release check). When no gates are configured, it falls back to a set of built-in checks across Jira, Confluence, Bitbucket, and Bamboo. Adding --discover runs additional aggregate checks across all repos discovered from Jira dev-status links.

​
Usage

cops release summary [flags]

​
Flags

​
--project
string
Project key from the projects map in cops.project.json. Defaults to defaultProject when set.
​
--fixVersion
string
Jira fixVersion label to evaluate (e.g. 2026-Q1). Falls back to release.jira.fixVersion in cops.project.json.
​
--jiraProject
string
Jira project key override (e.g. MYPROJ). Falls back to release.jira.projectKey.
​
--readyStatuses
string
Comma-separated Jira statuses treated as release-ready (e.g. Done,Closed). Defaults to Ready for Release,Done,Closed,Resolved.
​
--confluenceSpace
string
Confluence space key for the required release page check. Falls back to release.confluence.requiredPages[0].spaceKey.
​
--confluencePageTitle
string
Title of the required Confluence release page. Falls back to release.confluence.requiredPages[0].title, then Consolidated Deployment Steps.
​
--bitbucketProject
string
Bitbucket project key. Falls back to release.bitbucket.projectKey.
​
--bitbucketRepo
string
Bitbucket repository slug. Falls back to release.bitbucket.repo.
​
--releaseBranch
string
Release branch name (e.g. release/2026-03-13). Falls back to release.bitbucket.releaseBranch.
​
--bambooPlan
string
Bamboo plan key (e.g. PROJ-PLAN). Falls back to release.bamboo.requiredPlans[0].
​
--discover
boolean
default:"false"
Enable dynamic repo discovery. Discovers in-scope repos from Jira dev-status links and runs aggregate checks (release branch existence, open PR threshold, build signal) across each discovered repo.
​
--discoverBoard
number
Jira board ID for sprint-based discovery scope. When provided, the active sprint on this board determines the in-scope issues.
​
--discoverIssueTypes
string
Comma-separated issue types for discovery scope (e.g. Story,Defect). Defaults to Story.
​
--discoverSprintIds
string
Comma-separated sprint IDs to use as discovery scope (e.g. 101,102).
​
--discoverSprintStates
string
Comma-separated sprint states for board-based discovery: active, future, closed. Defaults to active.
​
--discoverMaxIssues
number
default:"500"
Maximum number of in-scope Jira issues to inspect for repo discovery.
​
--discoverMaxOpenToRelease
number
default:"0"
Maximum allowed open PRs per discovered repo targeting the release branch.
​
--output
string
default:"table"
Output format: table, json, or markdown.
​
--insecure
boolean
default:"false"
Disable TLS certificate validation. Use only with self-signed certificates in trusted networks.
​
--profile
string
Override the active config profile.

​
Built-in checks (no gates configured)

When cops.project.json has no release.gates, the command runs these built-in checks:
ProductCheckStatus logic
JiraStories exist for fixVersionpass when at least 1 story found; warn otherwise
JiraStories in release-ready statusespass when all stories are in readyStatuses; warn otherwise
ConfluenceRelease documentation page existspass when page found; warn otherwise
BitbucketRelease branch existspass when branch found; warn otherwise
BitbucketStory merge coverage to release branchpass when all story keys appear in merged PR branches/titles; warn otherwise
BambooBuild plan availabilitypass when plan is enabled and active; warn otherwise
BambooLatest build statepass when latest build state contains SUCCESS; warn otherwise

​
Discovery checks (--discover)

When --discover is set, additional checks run across repos found via Jira dev-status:
ProductCheck
JiraNumber of repos discovered and issues inspected
JiraIssues missing dev repo links
BambooDiscovered repos with Bamboo plan links
BambooDiscovered repos with deployment environment links
BitbucketRelease branch exists in each discovered repo
BitbucketOpen PR count is within threshold in each discovered repo
BitbucketLatest release-branch commit has a SUCCESS build signal

​
Exit codes

CodeMeaning
0All checks passed
20One or more checks failed or a blocking gate failed
10One or more checks produced a warn result

​
Examples

cops release summary

product     check                                status  details
──────────  ───────────────────────────────────  ──────  ──────────────────────────────────────────────
jira        Stories in fixVersion                pass    23 stories found
jira        Stories in release-ready statuses    pass    All stories are in release-ready status
confluence  Release documentation page           pass    Found page 'Consolidated Deployment Steps'
bitbucket   Release branch exists                pass    release/2026-03-13 exists
bitbucket   Story merge coverage to release branch  pass  23/23 stories linked to merged PRs
bamboo      Build plan availability              pass    PROJ-PLAN is enabled/active
bamboo      Latest build state                   pass    PROJ-PLAN-99: Successful

cops release check

Run individual release gates with exit-code control.

cops release repos discover

Discover repos from Jira dev-status links.

Build docs developers (and LLMs) love

Get started for freeTalk to us