One daily bug report that support, QA and engineering all trust
Your clone matches every open bug case to its engineering issue and tells each team what to do next.
Each day your clone lines up every open Salesforce bug case with its Linear issue, sorts them by where they are (shipped, ready for QA, in progress, in queue or not actionable), puts urgent ones first, and sends an email and channel post with status, ETA and next steps.
What your clone does
The same bug lives in two systems, so customer owners don't know what shipped and QA doesn't know what to test. Your clone keeps both sides in sync daily.
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 |
Who it helps
- 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.
How it runs
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.
Set it up, step by step
- Hand CLONE-INSTRUCTIONS.md to your clone: "Set this upShow me a plan first."
- The clone reports what is connected (discovery table)
- Answer the placeholder questions (section 6)
- Approve the planThe clone attaches Bug Report QA Report 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 runEstablishing 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).
The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.
Before you start
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 | Bug Report QA Report (prebuilt skill) | The report logic |
| 2 | Salesforce Case Operator | Read open Cases with Reason = Bug |
| 3 | Linear Operator | Read linked issues, status, labels, ETA |
| 4 | Google Gmail Operator 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 |
Good to know
- 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.
Questions, answered
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.
Ready when you are. So is your clone.
Build your clone, paste in the Daily Bug & QA Report instructions, and approve the plan it shows you.