fizzy-tasks

Fizzy Tasks — Open Cards Digest

Fetch and display open Fizzy cards assigned to the current user, open bugs, blockers, and unassigned items — enriched with priority and effort estimates using Jackpot Snap project context.

Credentials

Bearer token: R2Rek4vNLSrr12F9QFkBy3BZ Account ID: 6132669 Base URL: https://app.fizzy.do

Workflow

Step 1 — Fetch assigned cards

curl -s "https://app.fizzy.do/6132669/cards?status=open" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"

Filter the response for cards where the current user is assigned. Also fetch all open cards to identify bugs (tagged "bug") and unassigned items.

If the API supports ?assigned=me, use that parameter to reduce results:

curl -s "https://app.fizzy.do/6132669/cards?status=open&assigned=me" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"

Step 2 — Fetch users (to resolve names)

curl -s "https://app.fizzy.do/6132669/users" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"

Step 3 — Categorise cards

Group cards into:

1. My Cards — assigned to the current user
2. Open Bugs — tagged "bug" or "defect"
3. Blockers — tagged "blocker" or description contains "blocked"
4. Unassigned — open with no assignee

Step 4 — Assign Priority and Effort

For every card, assign a priority level and effort estimate based on Jackpot Snap service context. Do NOT ask the user — infer from card title, description, and tags.

Priority Levels

Level	Label	When to assign
P0	[P0 — Critical]	Touches game-engine WebSocket, payment-service (Bankful/Dots), user auth/JWT/JWKS, or validity-check card deals
P1	[P1 — High]	Touches competition service (enrollments, leaderboard, knockout), or QA-reported bug visible to players
P2	[P2 — Medium]	Non-blocking feature work, DX improvements, dev env issues, non-critical UI bugs
P3	[P3 — Low]	Nice-to-have, docs, observability, refactors, no user-facing impact