feat: ADO configurable work item types, area paths, and iteration support #240
Description
ADO Integration Enhancement: Configurable Work Item Types & Area Paths
Background
During external testing of the ADO platform adapter (PR #191), testers discovered that different ADO organizations use different work item types and project configurations:
- WDATP project uses custom locked-down types (Stories category is literally named "Do not create work items in this project")
- OS project uses
Scenarioinstead ofUser Story - Standard ADO projects may use
User Story,Bug,Task, etc.
Currently Squad hardcodes User Story as the work item type. This breaks in any non-standard ADO project.
Proposed Enhancements
P0 — Configurable work item type
- Add
workItemTypeoption to squad config (e.g.,workItemType: "Scenario"insquad.config.ts) - Auto-detect available work item types by querying the ADO process template
- Fall back to
User Storyif not configured
P1 — Area path configuration
- Add
areaPathoption to squad config so work items land in the correct team backlog - Current behavior: uses project default area path
P1 — Iteration path support
- Map sprints/iterations for ADO work items
- Allows work items to appear in the correct sprint board
P2 — Process template introspection
- Query the ADO process template to discover available work item types, fields, and states dynamically
- Handle ReadOnly fields gracefully (like WDATP's Activity field on Task Items)
Test Results Reference
Full test results: https://github.com/tamirdresher_microsoft/tamresearch1/issues/14
10/13 tests passed. 3 blocked by WDATP project restrictions (not Squad bugs).
3 bugs found during testing were already fixed in PR #191:
- ✅ GitHub workflows generated in ADO repos — fixed (init skips for ADO)
- ✅ No platform indicator in config — fixed (adds "platform": "azure-devops")
- ✅ MCP template references Trello — fixed (platform-appropriate examples)