1. Sign in and verify your role
Sign in with Google. Look at the top-right user badge:
- viewer: read-only
- product manager or editor: task editing enabled
If a control is disabled, your role does not allow that action.
2. Understand the two modes before editing
Use the top toggle button:
- Mode: Planning for editing and planning work
- Mode: Review for reviewing owners and pending Jira children
Keyboard shortcut: Cmd + M/Ctrl + Shift + M to switch instantly.
3. Planning mode: edit the plan
In Planning mode you can:
- add tasks (+ Add task)
- edit name/effort/dates/deadlines/tags
- reorder rows (manual sort)
- set cutoff and resources
Tip: double-click cells to open the edit dialog where relevant.
4. Set sprint scope correctly (very important)
Use Sprint cutoff in Planning Controls.
Everything below the red cutoff line is treated as out-of-sprint and excluded from sprint totals.
5. Set realistic team capacity
In Resources (developers), enter available developers per effort role. The app compares planned effort to capacity so you can spot overloads quickly.
6. Connect Jira (optional but recommended)
Open Tools → Jira: ... and fill:
- Jira base URL (for example: https://your-site.atlassian.net)
- API token
- Jira account email
Use the built-in Test button before saving.
7. Review mode: track progress and ownership
Switch to Review mode to see:
- % Done
- Owner
- optional Owner filter
Click any row to open pending child tickets (owner, status, summary).
8. Use filters to focus quickly
Use top summary cards and controls to narrow what you see (search, tags, owner filter in review mode). This helps run focused planning/review sessions.
9. Saving and exporting
Changes are auto-saved to the server. When you need a file snapshot, use Tools → Export .xlsx.
10. Recovery and audit tools
Use Tools → Recover local data only when needed (for restoration). Use Tools → Audit log to inspect change history.