# Requirements: Daily Bug & QA Report

> **Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 30–60 minutes**
>
> 🧩 **Based on the prebuilt skill `BugReport-QAReport`.** You attach it; you don't have to write it.

---

## 1. Required skills / operators

> Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

| # | Skill / operator (exact name) | Used for |
|---|---|---|
| 1 | **BugReport-QAReport** (prebuilt skill) | The report logic |
| 2 | **SalesforceCaseOperator** | Read open Cases with Reason = Bug |
| 3 | **Linear_Operator** | Read linked issues, status, labels, ETA |
| 4 | **GoogleGmailOperator** or the **Outlook email operator** | Send the HTML report |
| 5 | Slack or Microsoft Teams (clone messaging integration) | Post to `{TEAM_CHANNEL}` |
| 6 | **Scheduled task** (`platform`) | Daily run |

## 2. Connections and minimum permissions

| Connection | Minimum permission |
|---|---|
| Salesforce | **Read** Cases (including Reason, status, owner, custom link field if used) |
| Linear | **Read** issues, labels, states, due dates, descriptions |
| Gmail / Outlook | **Send** (to internal recipients) |
| Slack / Teams | **Post** to `{TEAM_CHANNEL}` |

All sign-ins are done by you. The clone never needs your password.

## 3. Optional add-ons

| Add-on | Adds |
|---|---|
| One-time backfill | Proposes case-to-issue links for existing bugs |
| Custom buckets/labels | Match your team's vocabulary |

No Salesforce to HubSpot mapping applies: this card is Salesforce only.

## 4. Data prerequisites

- [ ] Salesforce Cases have a Reason picklist value for bugs (for example "Bug"), used consistently
- [ ] A reliable case-to-issue link: case number in the Linear title/description, or Linear issue ID in a case field
- [ ] Urgent bugs carry a recognizable Linear label (for example DEFCON)
- [ ] Linear issues use standard states and have due dates where possible
- [ ] `{REPORT_RECIPIENTS}` are internal addresses

## 5. Roles and permissions

| Role | Needs |
|---|---|
| Support / CS lead | Salesforce read access, approves the plan |
| Ops / admin | Linear and messaging connection rights, can create scheduled tasks |
| Recipients | None |

## 6. Estimated setup time

| Task | Time |
|---|---|
| Check requirements | 5 min |
| Discovery and placeholders | 10 min |
| Connect Salesforce and Linear | 10–15 min |
| Attach skill, create schedule | 5 min |
| Test and review | 10–20 min |
| Total | 30–60 min (plus time to fix linking, if needed) |

## 7. Pre-flight checklist

- [ ] Salesforce and Linear accounts with read access
- [ ] Gmail or Outlook connected to the clone
- [ ] Slack or Teams channel chosen
- [ ] Link convention decided
- [ ] Recipients and run time decided

## 8. You're ready when…

- ✅ BugReport-QAReport is attached
- ✅ Salesforce and Linear are connected
- ✅ A daily scheduled task with "Run the daily bug report" exists
- ✅ An on-demand test report arrived by email and in the channel