Skip to main content
cops release repos discover queries Jira dev-status artifacts for each in-scope issue and extracts the Bitbucket repositories, Bamboo plan links, and deployment environment links referenced in branch and pull-request activity. Each discovered repo is then validated against Bitbucket.

​
Usage

cops release repos discover [flags]

​
Flags

​
--project
string
Project key from cops.project.json. When set, jiraProject and fixVersion defaults are read from the matching project configuration.
​
--jiraProject
string
Jira project key override (e.g. MYPROJ). Required when not using sprint scope and no project config is present.
​
--fixVersion
string
Jira fixVersion label to scope discovery (e.g. 2026-Q1). Required when using fixVersion scope (not sprint scope).
​
--board
number
Jira board ID. When provided, the active sprint(s) on this board determine the in-scope issues instead of --fixVersion.
​
--sprintIds
string
Comma-separated sprint IDs to use as discovery scope (e.g. 101,102). Takes precedence over --board sprint resolution.
​
--sprintStates
string
Sprint states for board-based scope. Comma-separated: active, future, closed. Defaults to active.
​
--issueTypes
string
Comma-separated issue types to include in scope (e.g. Story,Defect). Defaults to all types when omitted.
​
--maxIssues
number
default:"500"
Maximum number of in-scope issues to inspect for repo links.
​
--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.

​
Output columns

projectKey, repo, issuesLinked, validated, source, bambooPlans, deploymentEnvs, deploymentLinks, issueKeys
ColumnDescription
projectKeyBitbucket project key for the discovered repo
repoBitbucket repository slug
issuesLinkedNumber of in-scope Jira issues linked to this repo
validatedtrue when the repo was confirmed to exist in Bitbucket
sourceHow the repo was identified: dev-status (structured API data) or dev-status-url (URL pattern extraction)
bambooPlansBamboo plan keys found in dev-status deployment artifacts
deploymentEnvsDeployment environment names/IDs found in dev-status
deploymentLinksTotal number of deployment event links across in-scope issues
issueKeysJira issue keys linked to this repo

​
Scope modes

​
fixVersion scope

Used when --jiraProject and --fixVersion are provided (and no sprint flags). 
cops release repos discover --jiraProject MYPROJ --fixVersion 2026-Q1
The command runs a JQL query: 
project = MYPROJ AND fixVersion = "2026-Q1"

​
Sprint scope

Used when --board or --sprintIds is provided. In this mode --fixVersion is optional and acts as an additional filter. 
# Scope to active sprint on board 42
cops release repos discover --board 42

# Scope to specific sprint IDs
cops release repos discover --sprintIds 101,102

# Scope to active sprint, then filter by fixVersion
cops release repos discover --board 42 --fixVersion 2026-Q1

​
Exit codes

CodeMeaning
0Repos discovered and all in-scope issues have repo links
20No repos discovered
10Repos discovered but some in-scope issues are missing dev repo links

​
Examples

cops release repos discover --jiraProject MYPROJ --fixVersion 2026-Q1

projectKey  repo         issuesLinked  validated  source      bambooPlans  deploymentEnvs
──────────  ───────────  ────────────  ─────────  ──────────  ───────────  ──────────────
MYPROJ      my-service   14            true       dev-status  PROJ-PLAN    production#12345
MYPROJ      auth-lib     6             true       dev-status  PROJ-AUTH
Pass --output json and pipe the result to jq to extract repo slugs or bamboo plan keys for use in downstream pipeline steps.

cops release summary

Run summary with --discover to aggregate checks across discovered repos.

cops release check

Run release gates including Bitbucket and Bamboo checks.

Build docs developers (and LLMs) love

Get started for freeTalk to us