with the skill
## Ticket groups (12 tickets, Sep 2-17)
| Group | Tickets | Count |
|---|---|---|
| **Sync and data loss** | T-404, T-406, T-407, T-409, T-411, T-412 | 6 |
| **Billing** | T-401, T-405, T-410 | 3 |
| **Feature requests** | T-402 (dark mode), T-408 (calendar integration) | 2 |
| **Account access** | T-403 (password reset email) | 1 |
## Look at first: sync and data loss
**Evidence**
- Half of all tickets are in this group, and all 6 were filed on or after Sep 10, the day after v3.2 shipped.
- None of the 4 tickets before the release (Sep 2-5) mention sync.
- Three tickets tie the problem to the update: T-404 names v3.2, and T-407 and T-409 say "after the update" or "since the update".
- Two tickets report lost work: T-406 (offline edits lost) and T-412 (two days of edits lost).
- T-411 shows it affects shared notebooks, so it can hit collaborators too.
**Interpretation (not yet confirmed)**
- A v3.2 sync regression is the likely common cause. The duplicate notebooks, the endless spinner, and the missing cross-device edits could all come from one fault.
Show the rest (19 more lines)
- T-406, T-411, and T-412 don't mention the version, so I'm linking them by timing only. T-412 in particular could involve edits made before Sep 9.
**Suggested actions**
1. Have engineering check v3.2 sync changes against these 6 reports and look for a common root cause.
2. Contact the T-406 and T-412 users about recovering lost data. This is the most damaging and least reversible issue.
3. Consider a hotfix or rollback, and tell users to avoid offline editing until it's fixed.
4. Pull sync error rates and duplicate-notebook counts from analytics to see how widespread this is beyond the tickets.
## Then, in order
1. **T-401, double charge (Sep 2).** It's a single ticket, but it's a money error and is probably quick to fix. Refund it and check whether other customers were double-charged. T-405 (wrong company name on an invoice) is a similar billing-data fix.
2. **T-403, password reset email never arrives (Sep 5).** Only one report, but it locks the user out. Check email deliverability and spam logs, since a delivery problem would affect many users who never write in.
3. **T-410, annual plan refund.** This is a policy and support decision rather than a bug. Check whether the user is also affected by the sync issues, since that would explain the request.
4. **T-402 and T-408, feature requests.** Log them in the backlog. Neither is urgent, and there are only single requests, so there's no demand signal yet.
## Caveats
- With 12 tickets, these counts show direction but aren't statistically meaningful.
- I can't tell whether any tickets come from the same user, so "6 tickets" may mean fewer than 6 people.
- Tickets only capture users who contacted support. Actual impact may be larger, so the analytics check matters.