Leadership dashboard for SQA work. Zero dependencies (Node 18+).
npm start # http://localhost:4000 (ships with demo data)
| Tab | Answers |
|---|---|
| Overview | Status by project, blockers, overdue, unowned work, next 45 days, major/minor release mix |
| Resource alignment | Load per SQA owner vs capacity, owner x project heatmap, gaps (no owner, over capacity), site SPOCs |
| Projects | One row per project: progress, release (from -> to, major/minor), owners, JSON M/m, config count. Click for drill-down |
| JSON & config changes | Project x artifact matrix (Map, Zigbee, Charger, Station, Rack type, Storage strategy, ODS, Flow config, sys.local/consul) with MAJOR/minor counts + change log |
JFM Resource Planningis the live release log: one row per release (site, Major/Minor, from -> to version, SQA resource, QA status, risk, Solution QA out date). Drives the Overview, Resource alignment and Projects tabs. Use the period selector to scope it.Release_plannerholds task-level work (type, scope, owner, SQA dates). Open tasks whose SQA end date is more than 60 days old are shown as stale rather than counted as load.Current Live site version+Compliance/Non Compliance sitesfeed the Version map (current version per site, planned version, major/minor jump).Resource Planningfeeds site SPOC coverage.- Names are normalised: owners to first name (Khushi.n -> Khushi), projects via
projects.aliases/projects.prefixesinconfig.json.
Tabs used (names in config.json > sheet.tabs): Release_planner (tasks), JFM Resource Planning (per-site Major/Minor release + resource), Resource Planning (site SPOCs).
- API key: share the sheet "anyone with the link can view", create a Google API key with Sheets API enabled, put
GOOGLE_API_KEYin.env, set"source": "sheet". (Company sheets that can't be link-shared: useGOOGLE_ACCESS_TOKENfrom a service account/OAuth.) - Full export (what is used today): Drive -> download the workbook as .xlsx, then
python3 -I tools/xlsx_to_csv.py book.xlsx data/csv "Release_planner" "JFM Resource Planning" "Resource Planning" "Current Live site version" "Compliance/Non Compliance sites"(Google drops the/from tab names in the .xlsx, which the loader tolerates). Set"source": "csv". - CSV drop-in (no credentials): export each tab as CSV into
data/csv/<Tab name>.csv, set"source": "csv".
Columns are matched by header text, so reordering columns is safe.
Rules live in config.json > classification. A task is scanned when its type or text mentions json/config. Each artifact has a default level; words like new / add / remove / expansion promote JSON changes to major.
Override on any row by writing [major] or [minor] in the scope text (or Jira labels json-major / json-minor, config-update).
Review these defaults with the team - they are an assumption, not taken from the sheet.
A cleaner long-term fix: add explicit "JSON change level" and "Artifact" columns / Jira fields and map them.
config.json > jira.baseUrl=https://<org>.atlassian.net, setjira.jql..env:JIRA_EMAIL,JIRA_API_TOKEN(id.atlassian.com > Security > API tokens).- Map fields in
jira.fieldMap(project <- components/label/custom field, dates <- duedate/custom field ids). "taskSource": "both"while migrating, then"jira".
Issue -> task: status category -> Done / In Progress / Not Started (status name containing "block" -> Blocked); assignee -> SQA owner; description + summary feed the JSON/config classifier. Releases and site SPOCs still come from the sheet tabs until you move those to Jira too.
capacityPerPerson (open tasks before an owner is flagged), asOf (fix "today"; demo uses 2025-10-27), owners.aliases / projects.aliases (merge spelling variants such as "Sams LAX" and "LAX"), refreshSeconds (server cache; browser auto-refreshes every 5 min).