Daily Bug & QA Report
Every open Salesforce bug case reconciled against Linear, bucketed by lifecycle, with QA guidance, in your inbox and team channel each day.
The problem
Support and engineering track the same bug in two systems. CS owners don't know which fixes shipped, QA doesn't know what is ready to test, and customers wait for updates that were already possible to send.
Daily Bug & QA Report
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Intermediate · Setup time: 30–60 minutes
🧩 Based on the prebuilt skill
BugReport-QAReport. You attach it; you don't have to write it.
Your clone checks every open bug case in Salesforce against Linear each day and sends one clear report: what shipped, what is ready to test, what is stuck, and what to do next.
1. Overview and value
Bugs live in two places: a Salesforce Case that the customer-facing team owns, and a Linear issue that engineering owns. Nobody has the full picture. The Daily Bug & QA Report reconciles them for you.
Every day (and any time you ask), the clone:
- finds every open Salesforce Case with Reason = Bug (anything not Closed),
- looks up the linked Linear issue(s) for each,
- sorts bugs into lifecycle buckets,
- puts DEFCON / urgent-labeled bugs at the very top,
- writes, per bug: summary, status, ETA, suggested next action for the CS owner, and QA guidance (what to test),
- sends a branded HTML email to
{REPORT_RECIPIENTS}and posts to{TEAM_CHANNEL}.
| Bucket | Meaning | Typical next action |
|---|---|---|
| Closed & In Production | Fixed and live in Linear | Tell the customer, close the case |
| Ready for QA | Fix built, awaiting verification | QA tests, CS prepares the update |
| In Progress | Engineering is working on it | Share ETA if known |
| In Queue / Backlog | Not started | Push priority if the customer is impacted |
| Non-actionable | No usable link, canceled, duplicate or unclear | Fix the link or close the case |
2. Who it's for
- Support leads and CS owners who need to know when to update customers.
- QA and Ops who need a daily "what is ready to test" list.
- Customer Success leaders who want one view of bug health.
3. How it works
Daily schedule ("Run the daily bug report") or on demand
│
▼
┌─────────────────────────────────────────────────────────┐
│ BugReport-QAReport │
│ 1. Salesforce: open Cases, Reason = Bug, not Closed │
│ 2. Find linked Linear issue(s) per case │
│ 3. Read Linear status, labels, ETA │
│ 4. Bucket + DEFCON first + next action + QA guidance │
│ 5. Branded HTML email ──► {REPORT_RECIPIENTS} │
│ 6. Post summary ──► {TEAM_CHANNEL} │
└─────────────────────────────────────────────────────────┘The case-to-issue link is everything. The skill matches a case to an issue by either (a) the case number in the Linear issue title or description (for example "[Case 00012345]"), or (b) a Linear issue ID stored in a Salesforce case field. Cases without a link can't be matched and land in Non-actionable.
4. What the clone does (and never does)
Does: reads Cases and Linear issues, builds the report, emails internal recipients, posts to the team channel. Never: changes a case or Linear issue, emails customers, or closes cases on its own. Closing and customer updates are suggested actions for the CS owner.
5. Setup walkthrough
- Hand CLONE-INSTRUCTIONS.md to your clone: "Set this up. Show me a plan first."
- The clone reports what is connected (discovery table).
- Answer the placeholder questions (section 6).
- Approve the plan. The clone attaches BugReport-QAReport via the platform.
- You connect Salesforce and Linear (sign-in screens) and make sure Slack or Teams is available.
- The clone creates the daily scheduled task with the prompt "Run the daily bug report".
- Test on demand, review the first report, then let the schedule run.
Establishing the link. Pick one convention and tell your team: put the case number in every Linear bug title ("[Case 00012345] Export fails"). For existing bugs, the clone can propose a one-time backfill: list open bug cases with no matching Linear issue, suggest likely matches by title and account, and you approve any edits (it never edits without your yes).
6. Placeholders to decide
| Placeholder | Meaning | Example |
|---|---|---|
{REPORT_RECIPIENTS} | Internal email recipients | support-leads@yourcompany.com |
{TEAM_CHANNEL} | Slack or Teams channel for the post | #support-bugs |
{BUG_REASON_VALUE} | Salesforce Case Reason value for bugs | Bug |
{LINK_CONVENTION} | How cases and issues are linked | Case number in Linear title |
{URGENT_LABELS} | Linear labels meaning urgent | DEFCON 1, DEFCON 2, urgent |
{RUN_TIME} | Daily time and time zone | 8:00 AM, Mon–Fri, America/New_York |
7. What to expect
- A daily email titled with the date, urgent bugs first, then each bucket.
- A short channel post with counts and a link to the email.
- "Closed & In Production" is your customer-update to-do list.
- Early reports will show many Non-actionable items until linking improves.
8. Customizing
Rename buckets, change urgent labels, add recipients, change the run time, or ask for a weekly-only version. Ask the clone to adjust the scheduled prompt (for example "Only include bugs for accounts owned by {TEAM_NAME}").
9. Known gotchas
- Unlinked cases can't be matched. Fix the linking habit first.
- Keep the Reason picklist consistent. If "Bug" is spelled several ways, cases will be missed.
- Closed in Linear but open in Salesforce means the customer should be told and the case closed. The report flags these at the top of the Closed & In Production bucket.
- Internal recipients only. Don't add customers to
{REPORT_RECIPIENTS}. - Salesforce only. HubSpot isn't supported for this card.
10. FAQ
Does it work with HubSpot? No. It needs Salesforce Cases. Can I run it on demand? Yes: "Run the daily bug report". Will it email customers? No. Will it edit Linear or Salesforce? No. Can one case have several issues? Yes; the report shows the combined status and the slowest issue sets the bucket.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Everything is Non-actionable | No link convention in use | Adopt the convention, run the backfill |
| Some bugs missing | Reason value differs | Standardize the picklist |
| No email | Schedule missing or email not connected | Ask the clone to list scheduled tasks and check Gmail/Outlook |
| No channel post | Slack/Teams not available | Reconnect messaging |
| Wrong ETA | Linear issue has no due date | Add due dates in Linear |
Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Daily Bug & QA Report
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
>
> 🧩 **Based on the prebuilt skill `BugReport-QAReport`.** You attach it; you don't have to write it.
---
## 1. Role and goal
Set up the prebuilt skill **BugReport-QAReport**. When done, you reconcile open Salesforce Cases (Reason = Bug) against Linear daily and deliver an HTML email to `{REPORT_RECIPIENTS}` and a post to `{TEAM_CHANNEL}`. This is setup only. Salesforce only: if the user uses HubSpot, say it isn't supported for this card (no case operator) and stop.
## 2. Safety rules
1. Show a numbered plan and wait for an explicit "yes" before attaching, creating or changing anything.
2. Never ask for or handle passwords, API keys or tokens. The user connects via sign-in screens.
3. Never email customers. Only internal `{REPORT_RECIPIENTS}`, and test emails only after approval.
4. Read-only for Salesforce and Linear during setup and in the report. Any link backfill edits require a separate explicit "yes" per batch.
5. Use exact catalog names. Skill names can differ slightly between orgs.
## 3. Discovery
Use the `platform` tool to list skills, operators and connections; use `describeOperator` on each. Report:
| Item | Status (✅⚠️❌❓) | Exact name in catalog | Notes |
|---|---|---|---|
| BugReport-QAReport | | | |
| SalesforceCaseOperator | | | Check a "Bug" Reason value exists |
| Linear_Operator | | | |
| GoogleGmailOperator or Outlook email | | | |
| Slack or Teams | | | |
| Scheduled task (platform) | | | |
## 4. Collect placeholders
Ask once:
1. `{REPORT_RECIPIENTS}` (internal emails)
2. `{TEAM_CHANNEL}` (Slack or Teams)
3. `{BUG_REASON_VALUE}` (default "Bug")
4. `{LINK_CONVENTION}` (case number in Linear title/description, or Linear ID in a case field; name the field)
5. `{URGENT_LABELS}` (default DEFCON, urgent)
6. `{RUN_TIME}` with time zone
Confirm in a table (Placeholder / Value) before the plan.
## 5. What you can do yourself after approval
- Attach **BugReport-QAReport** via the `platform` tool.
- Create the daily scheduled task (section 7).
- Offer the one-time backfill (section 7).
If you can't attach the skill, tell the user: settings → Skills → find **BugReport-QAReport** in the catalog → Add → tell me "added".
## 6. What the user must do
1. **Connect Salesforce:** settings → Connections → Salesforce → sign in with an account that can read Cases.
2. **Connect Linear:** settings → Connections → Linear → sign in with read access.
3. **Gmail or Outlook:** confirm the clone's email connection can send.
4. **Slack or Teams:** confirm the clone can post to `{TEAM_CHANNEL}` (invite it to the channel if needed).
5. **Tell the team the link convention** (for example "[Case 00012345]" at the start of the Linear title).
## 7. Prebuilt skill: configure and run
**What BugReport-QAReport does, step by step:**
1. Query SalesforceCaseOperator for Cases with Reason = `{BUG_REASON_VALUE}` and Status not Closed.
2. For each, find linked Linear issue(s) via `{LINK_CONVENTION}` using Linear_Operator.
3. Read each issue's state, labels, due date or ETA.
4. Bucket: Closed & In Production, Ready for QA, In Progress, In Queue/Backlog, Non-actionable (unlinked, canceled, duplicate).
5. Put bugs with `{URGENT_LABELS}` at the top.
6. Per bug write: summary, status, ETA, suggested next action for the CS owner, QA guidance (what to test).
7. Flag cases closed in Linear but open in Salesforce: tell the customer and close the case.
8. Send a branded HTML email to `{REPORT_RECIPIENTS}`; post a summary to `{TEAM_CHANNEL}`.
9. If a call fails, retry once, then mark the source unavailable and say so in the report.
**Scheduled task:** create a daily task at `{RUN_TIME}` with this exact prompt:
```
Run the daily bug report
```
Optional customization lines (append only if the user asks):
```
Only include bugs for accounts owned by {TEAM_NAME}.
Post to {TEAM_CHANNEL} only when there are urgent bugs.
```
**One-time backfill (propose only):** list open bug cases with no Linear match; suggest candidate issues by title and account; present as a table; after the user says "yes" per batch, add the case number to the Linear issue title/description (or the issue ID to the case field). Never bulk-edit without approval.
## 8. Test plan
Use a test case and a test Linear issue if possible. Run "Run the daily bug report" on demand.
| Check | ☐ |
|---|---|
| Email arrived at `{REPORT_RECIPIENTS}` only | ☐ |
| Channel post appeared in `{TEAM_CHANNEL}` | ☐ |
| Urgent bugs are at the top | ☐ |
| A linked case lands in the right bucket | ☐ |
| An unlinked case is Non-actionable | ☐ |
| Each bug has next action and QA guidance | ☐ |
| Nothing was edited in Salesforce or Linear | ☐ |
| Scheduled task is listed with the right time zone | ☐ |
## 9. Final status checklist
- ✅ Done by me: skill attached, schedule created, test run
- ⏳ Waiting on you: Salesforce and Linear sign-in, channel access, link convention, backfill approval
- 💡 Optional next steps: custom buckets, per-team reports, weekly summary
Gotchas to repeat: unlinked cases can't be matched; keep the Reason picklist consistent; closed in Linear but open in CRM means tell the customer and close the case; internal recipients only.
Requirements
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
Was this use case helpful?
Thanks!