# 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 1. Hand **CLONE-INSTRUCTIONS.md** to your clone: "Set this up. Show me a plan first." 2. The clone reports what is connected (discovery table). 3. Answer the placeholder questions (section 6). 4. Approve the plan. The clone attaches **BugReport-QAReport** via the platform. 5. **You** connect Salesforce and Linear (sign-in screens) and make sure Slack or Teams is available. 6. The clone creates the **daily scheduled task** with the prompt "Run the daily bug report". 7. 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.