Sources · Qvantum NPI/CPI

How this list works — read once:

The rows in each lane are the sources the dashboard uses today. They are pre-filled and saved in this browser.
Pasting a link or dropping a file adds a new row — it never overwrites or replaces an existing one.
To swap a source: delete the old row (the × button), then add the new one.
A dropped file is read in your browser only to preview it and capture its filename. The browser can’t see the file’s folder — so keep its link in the row (that’s the canonical reference).
Nothing reaches the dashboard until you Download sources.json below and the refresh script reads it.

⚠︎ Getting the SharePoint files in — the part that isn’t automatic These links open in your browser because you’re signed in to Microsoft 365. A script can’t follow them: fetched without a login they return 403 “Access denied” (tested against the BOM link). Only Jira has a real API token; the SharePoint files don’t. So until a Microsoft 365 token is set up, each refresh:

Click the link in the row → it opens in SharePoint (you’re logged in) → Download.
Drop the downloaded file on its lane below to confirm it’s the right one — the page reads it locally and shows the number.
Put the file in the refresh script’s input folder and run the refresh.

The links change most weeks (e.g. Week25 → Week26, a new PAB deck) — keep each row’s link current: delete the old, add the new.

Want it fully automatic (no manual download)? That needs a Microsoft Graph token — a one-time Azure AD app your M365 admin registers (read access to the two sites), after which the script pulls these exact links itself via Graph’s /shares endpoint. Say the word and I’ll build the script side so it’s ready the moment the token exists.

Jira releases

paste link Link

Feeds the software-release cards (Display QD, App QHA). A link identifies which release; live work-item counts come from the refresh script (or preview a Jira CSV export below).

Link / path	File	What it feeds

Add a release

Adds a row. Paste a /projects/<KEY>/versions/<id> link — the note fills in automatically.

Preview only — drop a Jira CSV/XLSX export to check the counts

issue export with a Status column · does not add a row

BOM workbook

.xlsm / .xlsx Auto

Feeds the BOM mat. proj/XLSX column. The script reads the Database tab, column “Date of Order / Reserved”: of the dark-green BOM lines (Delivered set, real Article No), how many carry an order/reserved date.

Link / path	File	What it feeds

Add a workbook

…or drop the downloaded workbook to confirm it’s the right one

reads it locally & shows the BOM % · e.g. Project Ekeby 2013 BOM Week26.xlsm

NPI/CPI status slides

.pptx Best-effort

Feeds the project-card fields (PHO, status, milestones, risk…). The slide is unzipped and read here for a preview; the script maps its fields to the NPI schema.

Link / path	File	What it feeds

Add a status deck

…or drop the downloaded deck to confirm & preview its slides

a .pptx · reads it locally; if its name isn’t in the list yet it adds a row

Files are read locally with SheetJS (spreadsheets) and JSZip (.pptx). The BOM rule mirrors tools/bom_maturity.py. No network calls are made with your files; the source list lives in this browser’s storage and in the sources.json you export.