Jira Cloud conventions for Cloudbreak — project keys, Team field (customfield_10001), JQL with Atlassian team ids, mascot clan → module mapping, quarterly epic labels.
Use this playbook when answering Jira questions, writing JQL, or using Atlassian MCP/API against CB. Do not assume it is loaded for generic coding tasks; open .agent/skills/cb-jira/SKILL.md when Jira context is needed.
CB or CLOUDBREAK (prefer CB in JQL unless you specifically need the other).customfield_10001Team or cf[10001]{MASCOT} Clan (e.g. Raven Clan, Wolf Clan, Bear Clan).Clauses such as Team = "Raven Clan" typically return no rows. Filter with the Atlassian team id from issue JSON, the Jira UI, or your integration.
Example (Raven Clan):
project = CB AND Team = 575d3206-8e71-4f04-9e7e-18bb73a1a118-283 ORDER BY updated DESC
Resolve other clans’ ids from customfield_10001 on a representative issue (REST/MCP) or from Jira, depending on your permissions.
Same mapping as .agent/WORKFLOW.md and cb-junior-dev:
| Clan | Primary areas |
|---|---|
| Raven Clan | core/, freeipa/ |
| Wolf Clan | datalake/, environment/ |
| Duck Clan | redbeams/ |
| Bear Clan | autoscale/ |
| Hawk Clan | cloud-aws-*, cloud-azure/, cloud-gcp/ |
Q4FY26-CB.CB-XXXXX Subject so CI can link PRs to Jira (see root AGENTS.md — Operational mandates and Continuous integration).