ADO + az boards — Quick Reference &ZeroWidthSpace;

Heritage Community Hub work tracking runs in Azure DevOps Boards. This card covers the commands, formats, and checklists you need every day.

ADO coordinates &ZeroWidthSpace;

Field	Value
Organization	`https://dev.azure.com/hybridcloudsolutions`
Project	`Heritage Community Hub`
GitHub repo	`github.com/Heritage-Virginia/heritage-community-hub`

Session setup &ZeroWidthSpace;

powershell

# 1. Authenticate to Azure
az login

# 2. Load HCS secrets into session
. D:\git\platform\scripts\Load-HCSEnvironment.ps1

# 3. Set ADO defaults (run once per terminal session)
az devops configure --defaults `
  organization=https://dev.azure.com/hybridcloudsolutions `
  project="Heritage Community Hub"

az boards — common commands &ZeroWidthSpace;

View a work item &ZeroWidthSpace;

powershell

az boards work-item show --id <id>

Create a User Story &ZeroWidthSpace;

powershell

az boards work-item create `
  --type "User Story" `
  --title "Add invitation-code validation to registration endpoint" `
  --area "Heritage Community Hub\Platform" `
  --iteration "Heritage Community Hub\2026-Q3-S1" `
  --assigned-to "kris@hybridsolutions.cloud" `
  --fields "Priority=3" "Tags=identity"

Create a Task under a Story &ZeroWidthSpace;

powershell

az boards work-item create `
  --type Task `
  --title "Write migration for invitation_codes table" `
  --parent <story-id> `
  --area "Heritage Community Hub\Platform" `
  --iteration "Heritage Community Hub\2026-Q3-S1"

Update state &ZeroWidthSpace;

powershell

az boards work-item update --id <id> --state Active
az boards work-item update --id <id> --state Resolved
az boards work-item update --id <id> --state Closed

Add a comment &ZeroWidthSpace;

powershell

az boards work-item update --id <id> --discussion "Your comment here."

Assign a sprint &ZeroWidthSpace;

powershell

az boards work-item update --id <id> --iteration "Heritage Community Hub\2026-Q3-S1"

Link parent to child &ZeroWidthSpace;

powershell

az boards work-item relation add `
  --id <child-id> `
  --relation-type "System.LinkTypes.Hierarchy-Reverse" `
  --target-id <parent-id>

Query your active items &ZeroWidthSpace;

powershell

az boards query --wiql "SELECT [System.Id],[System.Title],[System.State] FROM WorkItems WHERE [System.AssignedTo]='kris@hybridsolutions.cloud' AND [System.State]='Active'"

Query current sprint &ZeroWidthSpace;

powershell

az boards query --wiql "SELECT [System.Id],[System.Title],[System.State] FROM WorkItems WHERE [System.TeamProject]='Heritage Community Hub' AND [System.IterationPath]='Heritage Community Hub\2026-Q3-S1' ORDER BY [System.State]"

Commit message format &ZeroWidthSpace;

text

type(scope): short description AB#<id>

Type	Use for
`feat`	New feature or capability
`fix`	Bug fix
`docs`	Documentation or ADR changes
`chore`	Dependency updates, config, tooling
`refactor`	Code restructuring without behavior change
`test`	Adding or updating tests

Examples:

text

feat(calendar): add recurring event RRULE support AB#47
fix(auth): handle expired Apple ID tokens AB#52
docs(adr): record auth provider decision AB#18
chore(deps): upgrade eslint to 9.x AB#71

Branch naming &ZeroWidthSpace;

text

feature/AB<id>-brief-slug
bugfix/AB<id>-brief-slug
hotfix/brief-slug

Examples:

text

feature/AB47-recurring-events
bugfix/AB61-calendar-rrule-parse
hotfix/dependency-security-patch

Work item hierarchy &ZeroWidthSpace;

text

Epic  (phase-level initiative, multi-sprint)
└── Feature  (deliverable within one sprint cycle, single owner)
    └── User Story  (one unit of work, one sprint, AC required)
        └── Task  (sub-action, no AC required)

Priority &ZeroWidthSpace;

Value	Meaning
1	Outage or security incident — drop everything
2	Blocks sprint work — fix today or within sprint
3	Normal sprint work (default)
4	Backlog — no deadline

Iterations &ZeroWidthSpace;

Pattern: Heritage Community Hub\YYYY-Q<n>-S<m>

Example	Dates (approx.)
`2026-Q3-S1`	Jul 7 – Jul 20, 2026
`2026-Q3-S2`	Jul 21 – Aug 3, 2026
`2026-Q3-S3`	Aug 4 – Aug 17, 2026
`2026-Q4-S1`	Oct 5 – Oct 18, 2026

Unscheduled backlog items stay at the project root iteration. Active items must have a sprint assigned.

Area paths &ZeroWidthSpace;

Area path	Work
`Platform`	Auth, RBAC, API, IaC, observability, shared packages, web shell, calendar/announcements/messaging, PM/process, ADRs/docs
`Web`	React web client, portal surfaces, design system
`Mobile`	React Native + Expo, push notifications, app-store pipelines
`Homeschool`	Parent/student accounts, Resource Library, High School Program
`Marketplace`	Member listings, vendor directory, browse/review flows
`Media`	Sermons & Music Hub, member-posted media, content library

Full paths: Heritage Community Hub\<area>. These six are the area paths provisioned in ADO — there is no \Calendar, \Project Management, or \Documentation (use \Platform + a tag).

Tags &ZeroWidthSpace;

Tag	Apply when
`platform`	Cross-cutting platform work
`calendar`	Calendar feature area
`homeschool`	Homeschool portal feature area
`marketplace`	Marketplace feature area
`mobile`	React Native / Expo
`identity`	Auth, RBAC, social login, Key Vault
`pipeline`	CI/CD, ADO pipeline YAML
`docs`	Documentation, ADRs
`security`	Security, COPPA, trust & safety
`infrastructure`	Bicep, Azure resources, IaC
`breaking`	Breaks an existing interface
`cross-repo`	Spans more than one repo

GitHub Issues — standard labels &ZeroWidthSpace;

Label	Color	Meaning
`ado-tracked`	blue	Issue has a linked ADO work item
`in-progress`	yellow	ADO item is actively being worked
`resolved`	green	ADO item resolved — pending close
`wont-fix`	grey	ADO item closed as won't fix
`needs-triage`	red	Issue received, ADO item not yet created
`cross-repo`	purple	Affects more than one repo

GitHub Issues are an intake mirror only. ADO is the source of truth.

New work item checklist &ZeroWidthSpace;

[ ] Title starts with a verb; [scope] prefix if cross-repo
[ ] Description: what, why now, in scope, out of scope
[ ] Acceptance Criteria (min 3 for Epic/Feature/Story; min 2 for Bug)
[ ] Type correct (Epic / Feature / Story / Bug / Task)
[ ] Priority set (default 3)
[ ] At least one tag applied
[ ] Area path set
[ ] Iteration assigned if Active; root if backlog
[ ] Parent linked (Story to Feature to Epic)
[ ] AB#<id> in commit/PR if work has started

Closing checklist &ZeroWidthSpace;

An item may only move to Closed when:

[ ] All Acceptance Criteria verified
[ ] Code committed and pipeline passed
[ ] Linked GitHub Issue updated (sync handles this automatically on state change)
[ ] Follow-up work items created if needed

Daily development checklists &ZeroWidthSpace;

Starting your day (5 minutes) &ZeroWidthSpace;

[ ] az login if Azure session expired
[ ] . D:\git\platform\scripts\Load-HCSEnvironment.ps1
[ ] Check ADO board for your Active items
[ ] git pull origin main — pull latest

During development &ZeroWidthSpace;

[ ] Commits reference AB#<id>
[ ] Branch name includes AB<id> prefix
[ ] ESLint + TypeScript pass before committing

End of day (3 minutes) &ZeroWidthSpace;

[ ] git push your branch
[ ] Add a comment to the ADO item with status or blockers
[ ] Open a PR if the feature is complete and tests pass
[ ] Update ADO state (Active to Resolved if done)

Git shortcuts (VS Code) &ZeroWidthSpace;

Action	Shortcut
Open Source Control panel	`Ctrl+Shift+G`
Open Command Palette	`Ctrl+Shift+P`
Create branch	`Ctrl+Shift+P` → `Git: Create Branch`
Push	`Ctrl+Shift+P` → `Git: Push`
Pull	`Ctrl+Shift+P` → `Git: Pull`
Create PR	`Ctrl+Shift+P` → `GitHub Pull Requests: Create Pull Request`
View PRs	`Ctrl+Shift+P` → `GitHub Pull Requests: Focus on Pull Requests View`
View Actions	`Ctrl+Shift+P` → `GitHub Actions: Focus on GitHub Actions View`
View ADO work items	`Ctrl+Shift+P` → `Azure Boards: View My Work Items`