daeworkEngineering
Bug triage
Reads new Sentry issues, finds the ones that matter and files them in Linear once you agree.
Sentry
Linear- Support inbox
It starts on its own
Bug triage · every weekday at 9:00. You wrote the job once; the routine sends it.
What it did
- Searched issues · Sentry
- Got issue details · Sentry
- Got issue details · Sentry
- Searched issues · Linear
- Read chat · Support inbox
What waited for you
- Create issues: Two issues in Linear, team Web.
Read the whole chat
- Bug triage · every weekday at 9:00: Triage new Sentry issues and check Linear for duplicates.
- Searched issues · Sentry · 4 new since yesterday
- Got issue details · Sentry · TypeError in export/csv.ts
- Got issue details · Sentry · Timeout on /api/reports
- Searched issues · Linear · no duplicates
- Read chat · Support inbox · Priya's report
- Bug triage
Sentry has four new issues since yesterday. Two matter:
1. TypeError in export/csv.ts: 212 events from 38 users since release 2.14. It is the bug Priya at Lumen wrote to support about.
2. Timeout on /api/reports: 61 events, only in workspaces with more than 50,000 rows.
The other two come from one browser extension. Linear has no open issue for either bug. Want me to file both for the web team?
- You
Yes, file both. CSV one is urgent.
- Waited for your OK: Create issues. Two issues in Linear, team Web.
- You
Approved.
- WEB-482
- WEB-482 CSV export fails over 10,000 rows · Todo · Urgent priority · Web
- TypeError: Cannot read properties of undefined (reading 'push') in export/csv.ts:88. - 212 events from 38 users since release 2.14 - Only on reports over 10,000 rows - Customer report: Priya at Lumen, Oct 18 Workaround sent to customers: export one month at a time.
- Bug triage
Filed WEB-482 (urgent) and WEB-483. Each links its Sentry issue. I told Support inbox, so Priya hears when the fix ships.
More Daes
