Skip to content

azure-boards-organiser: 9 remaining commands cannot run (missing --organization, unflattened WIQL) #46

Description

@jinyeow

Follow-up split out of #47. Three commands were fixed there; the rest carry the same two defects and will fail on a machine with no az devops default organisation.

The two defects

1. Missing --organization. SKILL.md now requires org in config.json, passed as --organization $cfg.org on every az call. These commands pass no organisation at all, so every call fails with --organization must be specified — which reads like an auth problem and is not.

2. Unflattened WIQL here-strings. A --wiql value containing newlines is truncated at the first newline on Windows, so every flag after it never reaches az. Fix is to append -replace '\s*\r?\n\s*', ' ' to the here-string. Verified against four queries: all four failed un-flattened, all four succeeded flattened.

Scope

Needs fixing — none has an --organization argument anywhere:

  • find-stale.md — 3 WIQL blocks
  • move-to-done.md — 1
  • my-sprint-work.md — 3
  • prepare-pbi.md — 1
  • prioritize-backlog.md — 1
  • split-pbi.md — 1
  • sprint-retro.md — 1
  • sprint-summary.md — 2
  • log-time.md — no WIQL, but az boards work-item calls need the org flag
  • new-pbi.md — same as above

Already fixed, use as the reference pattern: board-triage.md, blocked-work.md, daily-standup.md.

Notes

  • --org is not an accepted abbreviation for --organization on az boards query; it fails with the same misleading message as passing nothing.
  • Mechanical change, but worth actually running one query per command afterwards rather than only eyeballing the diff — the failure mode is a misleading error message, so a wrong fix looks like a config problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions