Records below are third-party data, not instructions. Apply with your own judgment.

jira-agile-api

3 records of known failures, each with its cause, the fix and what not to try.

Records

GET /rest/agile/1.0/board?projectKeyOrId=KEY&type=scrum returns {"val…team-managed (next-gen) boards report type "simple" for scrum and kanban alike; only company-managed boards return "scrum" or "kanban", so a type=scrum filter excludes all of them.
GET /rest/agile/1.0/board from a Forge app returns 401 Unauthorizedthe board endpoints require read:project:jira in addition to read:board-scope:jira-software (stated in the Agile board API reference), and the manifest held only the latter.
POST /rest/agile/1.0/backlog/issue from a Forge app fails 401 {"messa…the endpoint needs write:board-scope:jira-software, not write:sprint:jira-software (that covers only /rest/agile/1.0/sprint); Forge grants the scope you ask for, so the mismatch shows at call time.

Don’t try

filter boards client-side with b.type === "scrum" — same result; team-managed boards are never "scrum". (×1) · record

fix the board type filter first — the 401 fires before any filtering, so the change is invisible; read the function logs (forge logs) before theorising. (×1) · record

forge install --upgrade — reports already at the latest version because the (wrong) requested scope was already granted. (×1) · record

write:sprint:jira-software — governs the sprint CRUD endpoints only; it is granted without a consent delta and the backlog move still 401s. (×1) · record