Chatbot — QA BAU
Standing QA workstream for the BOT squad. Not a product initiative, bucket, or
capacity-estimated program. No PRDs, no roadmap ## Priority row, no effort_*_days.
| Current Epic | BOT-4609 — 26Q3 QA Automation & Delivery |
| Project | BOT |
| Owners | Tito Amanda (automation lead) · Izzul (deployment-verification lead) |
| Peers | CDP TF-3521 · Bifrost BIF-8869 |
What belongs here
| Workstream | Practice | Outcome |
|---|---|---|
| Increase automation coverage | Regression gaps from shipped changes, retests, escaped defects; stabilize flaky tests/data | Release-critical flows have reliable automated coverage |
| Support regular deployments | Pre-release scope/env readiness, agreed checks, post-deploy smoke; report result or blocker | Each deployment has timely QA confidence and a recorded outcome |
| Test ops (as needed) | Testcase-management migration, suite hygiene, tooling that unblocks the two streams above | QA can execute without process/tooling drag |
What does not belong here
| Work | Route instead |
|---|---|
| Feature / initiative human QA (story acceptance) | Product initiative's executable Epic + Task/Bug split from that Story |
| Eng-owned test infra, MCP, hooks, repo skills | Code Readiness · BOT-4500 |
| Runtime/framework/security modernization | Engineering Initiatives · BOT-4620 |
| Product defects found in verification | File Bug under the product executable Epic (and split-from Story when known); optional link from the BAU verification Task |
Jira item contract
For every discrete BAU outcome, create a Jira item before starting work (manual / AI-assisted;
never jira-sync / main-full):
- Project
BOT· parent Epic = currentjira_epicon this file (today BOT-4609). - Type:
Taskfor planned automation or deployment support ·Bugonly when BAU itself is broken (tooling); product defects use the product Epic (table above). - Sprint: put finish-this-window work on the active Chatbot board sprint; else leave backlog.
- Summary prefix (required):
QA Automation — <flow> regression coverageQA Deployment Support — <service/release> verification
- Body: assignee (Tito or Izzul); affected service/flow; related initiative/release/incident when applicable; gap or deploy trigger; checks to run; expected evidence (run result, smoke, defect keys).
- Done note: outcome, residual risk, follow-up keys.
BAU Tasks do not require PRD user-story Stories under this Epic. Optional local Stories under the quarter Epic are allowed only as QA planning containers — never as product AC mirrors.
Quarter Epic rollover
The workstream is durable; the Jira Epic is not. One container Epic per planning quarter.
| Step | When | Action |
|---|---|---|
| 1. Mint | First sprint of the new quarter (or last week of the old) | Create Epic in BOT: summary 26Qn BOT - QA Automation Coverage & Deployment Support (match CDP/Bifrost naming). Copy Project Criticality from a sibling BOT Epic if required. |
| 2. Point | Same change | Set this file's jira_epic: + target_quarter: to the new key/quarter. |
| 3. History | Same change | Append the previous Epic to ## Epic history with status: superseded and end date. |
| 4. Close prior | When prior-quarter BAU Tasks are Done/Won't Fix | Transition prior Epic to Done (or leave In Progress only if stragglers remain — do not parent new work to it). |
| 5. Mirrors | Same change | Sprint plans cite the new key; capacity note stays generic ("current Epic on qa-bau.md"). |
| 6. Do not | — | Reuse the old Epic across quarters; renumber history rows; create an initiative folder for BAU. |
Open BAU Tasks still in flight at quarter boundary: finish under the old Epic, or move parent to the new Epic only when the work clearly belongs to the new quarter (prefer finish-in-place).
Epic history
| Quarter | Epic | Status | Notes |
|---|---|---|---|
| 2026-Q2 | BOT-3972 | superseded (Done) | 26Q2 QA Automation & Delivery |
| 2026-Q3 | BOT-4609 | current | 26Q3 QA Automation & Delivery |
| 2026-Q4 | TBD | — | Mint at Q4 start; then move jira_epic here |
Alignment & drift
- Expected off initiative-map.
jira-alignment-check/sprint-drift-auditmust treat the currentjira_epic(and history keys) as a known non-initiative Epic — not D9 classification drift and not epic-wiring-drift to "fix" by reparenting onto a product initiative. - Allow-list source of truth: this file's
jira_epic+## Epic history, mirrored on../README.md## Jira work routing.
Capacity
QA BAU fills gaps between initiative QA. It is not sized as initiative effort_qa_days.
See capacity.md QA rows — load stays initiative-driven; BAU is explicit slack use.