Skip to main content

Milestone Overview

GospeLib development is organized into 30 milestones (M00--M29) spanning foundation infrastructure through mobile delivery. Milestones M00--M14 follow the original sprint-based timeline; M15+ were added during the A1 amendment and later planning phases with dates TBD. Each milestone has a dedicated detail page linked below.

Milestone Summary​

MilestoneNameStatusDescription
M00Tech PrepCompleteDev environment, toolchain, monorepo scaffold
M01Data PipelineCompleteIngest CLI, corpus validation, test suite
M02Content APICompleteContent service, gateway, shared types and SDK
M03Scripture ReaderCompleteReader core, UI foundation, interaction layer
M04AnnotationsCompleteAuth integration, annotations and study tools
M05Search & StagingCompleteFull-text search, footnotes and cross-references
M06Interlinear & Lexicon22%Hebrew/Greek interlinear display, lexicon UI
M07JST Interlinear40%JST variant alignment and interlinear view
M08Knowledge Graph25%Graph-based entity and relationship explorer
M09AI Study AssistantCompleteLLM-powered study assistant integration
M10MonetizationCompleteBilling, subscriptions, Come Follow Me, sharing
M11Launch ReadinessCompleteOnboarding, polish, production infra, legal
M12Documentation SiteCompleteDocusaurus scaffold, API reference, blog
M13Multi-Translation & Schema EvolutionCompleteSchema fixes, translation support, enrichment
M14Corpus HarmonizationCompleteCross-corpus alignment and normalization
M15A1 Cleanup & Data Foundation93%Contradiction removal, data and label alignment
M16GUI Infrastructure & Layout87%Plugin architecture, application shell restructure
M17Core UX91%Hover cards, toolbars, Pinboard
M18Navigation SurfacesCompleteNavigation components, command palette and history
M19Integration & PolishCompleteFeature integration, accessibility and motion
M20Pipeline & Schema AlignmentCompletePipeline completion, package and schema alignment
M21Performance, Testing & MobileCompletePerformance, testing infrastructure, mobile adaptation
M22Session Advanced FeaturesCompleteAdvanced session management capabilities
M23Study Map -- Core89%Study map visualization and core navigation
M24Study Map -- Integration & ToolsCompleteStudy map tool integration and workflows
M25Advanced Study Plugins80%Scholarly and advanced study plugin suite
M26Plugin EcosystemCompletePlugin registry, distribution, third-party support
M27Desktop Application0%Electron/Tauri desktop packaging
M28Mobile Foundation13%Expo/React Native foundation and shell
M29Mobile Features0%Mobile-specific features and offline support

Project Timeline​

Project Start: Monday, March 9, 2026 (Week 1) Sprint Cadence: 2-week sprints

Note (2026-06-08): The original March 2026 timeline below is outdated. Actual completion dates for finished milestones are recorded in the milestone issue frontmatter (completed: field). Sprint references (S0--S18) and due dates for M00--M13 are historical and no longer tracked.

ZenHub Configuration Reference

ZenHub Registry​

All ZenHub entity IDs and configurations for MCP automation. IDs are opaque base64 strings resolved at runtime -- included here for reference and automation scripts.

Workspace & Repository​

EntityNameZenhub ID
OrganizationGospeLibZ2lkOi8vcmFwdG9yL1plbmh1Yk9yZ2FuaXphdGlvbi8xNjU4MzY
Zenhub WorkspaceGospeLib Web App MVPZ2lkOi8vcmFwdG9yL1JlcG9zaXRvcnkvMTM0NzU4NjMx
GitHub RepositoryGospeLib/mainZ2lkOi8vcmFwdG9yL1JlcG9zaXRvcnkvMTM0NzU4NjMy

Issue Type Hierarchy​

Zenhub enforces a 5-level hierarchy. Parent-child relationships must respect level ordering (L1 -> L2 -> L3 -> L4 -> L5).

LevelTypeZenhub IDUsed For
L1InitiativeZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3NzQTop-level product initiative (GospeLib MVP)
L2ProjectZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3NzUPhase groupings (Foundation, Reader, etc.)
L3EpicZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3NzYFeature areas within milestones (25 epics)
L4FeatureZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3ODMNew capabilities, user-facing functionality
L4TaskZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3ODEChores, infrastructure, tests, docs
L4BugZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3ODIDefects, regressions
L5Sub-taskZ2lkOi8vcmFwdG9yL0lzc3VlVHlwZS8zODU3ODADecomposed work items under L4 issues

Pipelines​

PipelineZenhub IDDescription
New IssuesZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNDUTriage queue -- review and estimate before backlog
IceboxZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNDYLow priority, not near-term
Product BacklogZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNDcReviewed, estimated, prioritized top-to-bottom
Sprint BacklogZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNDgReady for the current sprint, prioritized
In ProgressZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNDkActively being worked on
Review/QAZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNTACode complete, pending review/testing
DoneZ2lkOi8vcmFwdG9yL1BpcGVsaW5lLzM1NDUxNTETested and ready to deploy

Sprints​

2-week cadence. Sprint identifiers (S0--S18) map to Zenhub sprint entities.

SprintDatesZenhub NameZenhub IDMilestones
S0Mar 9--22Sprint: Mar 8 - Mar 22, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODIzM00, M12
S1Mar 23 -- Apr 5Sprint: Mar 22 - Apr 5, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODI0M01
S2Apr 6--19Sprint: Apr 5 - Apr 19, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODI1M01, M13
S3Apr 20 -- May 3Sprint: Apr 19 - May 3, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODI2M01, M02, M13
S4May 4--17Sprint: May 3 - May 17, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODI3M02, M03, M13
S5May 18--31Sprint: May 17 - May 31, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODI4M03, M13
S6Jun 1--14Sprint: May 31 - Jun 14, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODI5M03, M04
S7Jun 15--28Sprint: Jun 14 - Jun 28, 2026Z2lkOi8vcmFwdG9yL1NwcmludC80NzQyODMwM04
S8Jun 29 -- Jul 12--CreateM05, M06, M13
S9Jul 13--26--CreateM05, M06, M13
S10Jul 27 -- Aug 9--CreateM06, M13
S11Aug 10--23--CreateM06, M07
S12Aug 24 -- Sep 6--CreateM07, M08, M13
S13Sep 7--20--CreateM08, M09
S14Sep 21 -- Oct 4--CreateM08, M09, M10
S15Oct 5--18--CreateM08, M09, M10
S16Oct 19 -- Nov 1--CreateM10, M11
S17Nov 2--15--CreateM11
S18Nov 16--29--CreateM11

Milestones​

GitHub milestones set on the repository. Each maps 1:1 to a milestone markdown file.

MilestoneDue DateFile
M00: Tech Prep2026-03-22docs/milestones/M00-tech-prep.md
M01: Data Pipeline2026-05-03docs/milestones/M01-data-pipeline.md
M02: Content API2026-05-17docs/milestones/M02-content-api.md
M03: Scripture Reader2026-06-14docs/milestones/M03-scripture-reader.md
M04: Annotations2026-07-05docs/milestones/M04-annotations.md
M05: Search & Staging2026-07-26docs/milestones/M05-search-staging.md
M06: Interlinear & Lexicon2026-08-23docs/milestones/M06-interlinear-lexicon.md
M07: JST Interlinear2026-09-13docs/milestones/M07-jst-interlinear.md
M08: Knowledge Graph2026-10-18docs/milestones/M08-knowledge-graph.md
M09: AI Study Assistant2026-10-18docs/milestones/M09-ai-study-assistant.md
M10: Monetization2026-11-01docs/milestones/M10-monetization.md
M11: Launch Readiness2026-11-29docs/milestones/M11-launch-readiness.md
M12: Documentation Site2026-03-22docs/milestones/M12-documentation-site.md
M13: Multi-Translation & Schema Evolution2026-09-06docs/milestones/M13-multi-translation-schema.md
M14: Corpus Harmonization2026-06-14docs/milestones/M14-corpus-harmonization.md
M15: A1 Cleanup & Data FoundationTBDdocs/milestones/M15-a1-cleanup-data.md
M16: GUI Infrastructure & LayoutTBDdocs/milestones/M16-gui-infrastructure.md
M17: Core UXTBDdocs/milestones/M17-core-ux.md
M18: Navigation SurfacesTBDdocs/milestones/M18-navigation-surfaces.md
M19: Integration & PolishTBDdocs/milestones/M19-integration-polish.md
M20: Pipeline & Schema AlignmentTBDdocs/milestones/M20-pipeline-schema.md
M21: Performance, Testing & MobileTBDdocs/milestones/M21-performance-mobile.md
M22: Session Advanced FeaturesTBDdocs/milestones/M22-session-advanced.md
M23: Study Map -- CoreTBDdocs/milestones/M23-study-map-core.md
M24: Study Map -- Integration & ToolsTBDdocs/milestones/M24-study-map-integration.md
M25: Advanced Study PluginsTBDdocs/milestones/M25-advanced-plugins.md
M26: Plugin EcosystemTBDdocs/milestones/M26-plugin-ecosystem.md
M27: Desktop ApplicationTBDdocs/milestones/M27-desktop.md
M28: Mobile FoundationTBDdocs/milestones/M28-mobile-foundation.md
M29: Mobile FeaturesTBDdocs/milestones/M29-mobile-features.md

Labels​

All GitHub labels to create on the repository. No other labels should exist.

LabelColorCategoryDescription
Gateway#2C5F8AServiceGo API gateway service
Content#2C5F8AServicePython scripture graph queries
Auth#2C5F8AServiceGo auth/Clerk wrapper
Billing#2C5F8AServiceGo Stripe subscriptions
AI#2C5F8AServicePython LLM study assistant
Notifications#2C5F8AServiceGo push/email notifications
Ingest#2C5F8AServicePython CLI data pipeline
Web#3D6B4FAppNext.js web app
Mobile#3D6B4FAppExpo/React Native mobile app
Admin#3D6B4FAppNext.js admin dashboard
UI#7B68EEPackage@gospelib/ui component library
SDK#7B68EEPackage@gospelib/sdk client SDK
Types#7B68EEPackage@gospelib/types shared types
Config#7B68EEPackage@gospelib/config env schemas
Testing#7B68EEPackage@gospelib/testing test helpers
Go#D2691ELanguageGo source code
Python#D2691ELanguagePython source code
TypeScript#D2691ELanguageTypeScript/React source code
Infrastructure#808080ScopeDocker, Terraform, K8s, CI/CD infra
CI/CD#808080ScopeGitHub Actions, pipelines, deployment
Documentation#808080ScopeDocs, ADRs, specs, guides

Projects (L2)​

Zenhub Projects group epics by development phase. Each Project is an L2 issue type that parents multiple L3 Epics.

ProjectPhaseMilestonesStart DateEnd DateEpics
FoundationP0M00--M02, M132026-03-092026-05-17Tech Prep Foundation, Ingest Core Pipeline, Ingest Test Suite, Corpus Validation, Content Service API, Gateway Core, Shared Types & SDK, Schema Foundation & Critical Fixes, Content Service Translation Support
ReaderP1M03--M052026-05-042026-07-26Scripture Reader Core, UI Foundation, Reader Interaction, Auth Integration, Annotations & Study Tools, Full-Text Search, Footnotes & Cross-References
EnhancementP2M06--M09, M132026-07-132026-10-18Interlinear & Lexicon, JST Interlinear, Knowledge Graph, AI Study Assistant, Word Alignment & Lexicon Enrichment, Citation Extraction
LaunchP3M10--M122026-09-212026-11-29Billing & Subscriptions, Come Follow Me, Social Sharing, User Onboarding, UI Polish & Performance, Production Infrastructure, Legal & Compliance, Docusaurus Scaffold & Content Migration, API Reference & Search, Blog & Deployment

Epics (L3)​

Each Epic is an L3 issue type parenting the L4 issues within its scope. Dates are derived from the sprint range of their child issues.

EpicMilestoneParent ProjectStart DateEnd DateIssues
Tech Prep FoundationM00Foundation2026-03-092026-03-2213
Ingest Core PipelineM01Foundation2026-03-232026-05-0313
Ingest Test SuiteM01Foundation2026-04-202026-05-033
Corpus ValidationM01Foundation2026-04-202026-05-036
Content Service APIM02Foundation2026-04-202026-05-177
Gateway CoreM02Foundation2026-05-042026-05-173
Shared Types & SDKM02Foundation2026-04-202026-05-179
Scripture Reader CoreM03Reader2026-05-042026-06-148
UI FoundationM03Reader2026-05-042026-06-148
Reader InteractionM03Reader2026-06-012026-06-146
Auth IntegrationM04Reader2026-06-012026-06-283
Annotations & Study ToolsM04Reader2026-06-152026-07-057
Full-Text SearchM05Reader2026-06-292026-07-269
Footnotes & Cross-ReferencesM05Reader2026-06-292026-07-264
Interlinear & LexiconM06Enhancement2026-06-292026-08-239
JST InterlinearM07Enhancement2026-08-102026-09-065
Knowledge GraphM08Enhancement2026-08-242026-10-188
AI Study AssistantM09Enhancement2026-09-072026-10-189
Billing & SubscriptionsM10Launch2026-09-212026-11-017
Come Follow MeM10Launch2026-10-052026-11-013
Social SharingM10Launch2026-10-192026-11-012
User OnboardingM11Launch2026-10-192026-11-013
UI Polish & PerformanceM11Launch2026-10-192026-11-153
Production InfrastructureM11Launch2026-11-022026-11-294
Legal & ComplianceM11Launch2026-11-162026-11-292
Docusaurus Scaffold & Content MigrationM12Launch2026-03-092026-03-2212
API Reference & SearchM12Launch2026-03-092026-03-224
Blog & DeploymentM12Launch2026-03-092026-03-225
Schema Foundation & Critical FixesM13Foundation2026-04-062026-05-0312
Content Service Translation SupportM13Foundation2026-05-042026-05-316
Word Alignment & Lexicon EnrichmentM13Enhancement2026-06-292026-08-094
Citation ExtractionM13Enhancement2026-08-242026-09-064
A1 Contradiction RemovalM15A1 AmendmentTBDTBD8
Data Foundation & Label AlignmentM15A1 AmendmentTBDTBD7
Plugin & Composition ArchitectureM16A1 AmendmentTBDTBD9
Application Shell RestructureM16A1 AmendmentTBDTBD5
Hover Card SystemM17A1 AmendmentTBDTBD4
Toolbar SystemM17A1 AmendmentTBDTBD2
Pinboard & ComparisonM17A1 AmendmentTBDTBD5
Navigation SurfacesM18A1 AmendmentTBDTBD6
Command Palette & HistoryM18A1 AmendmentTBDTBD3
Feature IntegrationM19A1 AmendmentTBDTBD9
Accessibility & MotionM19A1 AmendmentTBDTBD4
Pipeline CompletionM20A1 AmendmentTBDTBD8
Package & Schema AlignmentM20A1 AmendmentTBDTBD4
Performance & TestingM21A1 AmendmentTBDTBD5
Mobile AdaptationM21A1 AmendmentTBDTBD3
Session Advanced FeaturesM22A1 AmendmentTBDTBD3
Study Map CoreM23Study MapTBDTBD9
Study Map Integration & ToolsM24Study MapTBDTBD7
Advanced Study PluginsM25ScholarlyTBDTBD5
Plugin EcosystemM26PluginsTBDTBD8
Desktop ApplicationM27DesktopTBDTBD3
Mobile FoundationM28MobileTBDTBD4
Mobile FeaturesM29MobileTBDTBD5

Initiative (L1)​

InitiativeDescriptionProjects
GospeLib MVPScripture study platform -- full-text, graph-based, AI-powered access to LDS canon + scholarly resourcesFoundation, Reader, Enhancement, Launch

Team​

MemberGitHub LoginZenhub ID
Lance MillerlellimecnarZ2lkOi8vcmFwdG9yL1plbmh1YlVzZXIvNjczNTY0

Priority Scale​

Zenhub's native priority field. Set via updateIssue.

PriorityCodeDescription
CriticalP0Absolute blocker -- milestone cannot ship without this
HighP1Important -- expected to ship within the milestone
MediumP2Nice to have -- may defer if time is short
LowP3Post-MVP or stretch goal

Estimate Scale​

Story points set via setIssueEstimate. Fibonacci-adjacent scale.

PointsRelative SizeExamples
1TrivialConfig change, typo fix
2SmallSimple chore, scaffolding
3Medium-smallSingle-service utility, test suite
5MediumStandard feature, API endpoint
8LargeComplex feature, multi-service
13Extra-largeMajor subsystem, critical path
Enhancement Rules (Issue Metadata Conventions)

1. Label System​

Labels are only for metadata that Zenhub does not handle natively. The following are managed by Zenhub and must never appear as labels:

  • Issue Type -> setIssueType
  • Priority -> native Zenhub priority field
  • Milestone -> GitHub milestones
  • Epic membership -> setParentForIssues
  • Estimate -> setIssueEstimate
  • Sprint -> addIssuesToSprints
  • Pipeline -> moveIssueToPipeline
  • Dependencies -> createBlockage

The full label list with colors is in the ZenHub Registry > Labels section above. In particular, no type:*, priority:*, epic:*, service:*, or lang:* labels -- only clean, readable names.

2. Epic & Project Hierarchy​

Epics use clean, human-readable titles -- not label-style epic:name slugs. The complete list of all epics, their parent projects, milestones, and date ranges is in the ZenHub Registry > Epics (L3) section above.

The full hierarchy is: Initiative (L1) -> Project (L2) -> Epic (L3) -> Feature/Task/Bug (L4) -> Sub-task (L5). Parent-child relationships are managed via setParentForIssues. Issue types are set via setIssueType using the IDs in the ZenHub Registry > Issue Type Hierarchy table.

3. Issue Type Mapping​

All issue types are managed via the native Zenhub Issue Type field (setIssueType), not labels. See ZenHub Registry > Issue Type Hierarchy for IDs.

Old LabelZenhub Issue Type
type:featureFeature
type:choreTask
type:infraTask
type:testTask
type:docsTask
type:designFeature
type:bugBug

Sub-task is also available for use in Sub-Issues tables (see section 7).

4. Milestone-Level ZenHub Config​

Each milestone file begins with a ZenHub Configuration table after the header and Phase Context section:

## ZenHub Configuration

| Field                | Value                |
| -------------------- | -------------------- |
| **Milestone**        | M00: Tech Prep       |
| **Due Date**         | 2026-03-22           |
| **Default Pipeline** | Product Backlog      |
| **Primary Epic(s)**  | Tech Prep Foundation |

Fields map directly to Zenhub/GitHub native features. Release info, if needed, belongs in the Phase Context prose -- not in this table.

5. Issue Metadata Format​

Each issue uses a compact metadata table containing only fields that map to MCP tool calls:

#### M00-001. Dev Environment Validation

| Field        | Value                        |
| ------------ | ---------------------------- |
| **Type**     | Task                         |
| **Epic**     | Tech Prep Foundation         |
| **Priority** | P0: Critical                 |
| **Estimate** | 3                            |
| **Sprint**   | S0                           |
| **Pipeline** | Product Backlog              |
| **Labels**   | `Go`, `Python`, `TypeScript` |

Rules:

  • Type -- one of: Feature, Task, Bug, Sub-task (maps to setIssueType)
  • Epic -- the clean epic title (maps to setParentForIssues)
  • Priority -- P0: Critical, P1: High, P2: Medium, P3: Low (maps to native Zenhub priority)
  • Estimate -- integer story points (maps to setIssueEstimate)
  • Sprint -- sprint identifier e.g. S0, S1--S2 (maps to addIssuesToSprints)
  • Pipeline -- Product Backlog, Sprint Backlog, In Progress, etc. (maps to moveIssueToPipeline)
  • Labels -- only service/app/package/language/scope labels from section 1 (maps to createGitHubIssue labels param)

Omitted fields (inherited or not applicable):

  • Milestone -- inherited from the file; set via GitHub milestone
  • Assignee -- assigned at sprint planning, not in spec
  • Dates -- set on Epics/Projects, not individual issues

6. Dependencies​

Dependencies map directly to createBlockage(blockedIssueId, blockingIssueId) MCP calls.

Compact format (preferred when context is obvious):

##### Dependencies

| Blocked By | Blocks                    |
| ---------- | ------------------------- |
| --         | M00-002, M00-003, M00-004 |

Detailed format (when relationships need explanation):

##### Dependencies

| Relationship | Issue   | Title                      |
| ------------ | ------- | -------------------------- |
| Blocked by   | M00-001 | Dev Environment Validation |
| Blocks       | M00-003 | Initial PostgreSQL Schemas |

If there are no dependencies:

##### Dependencies

None.

Milestone-Level Dependency Graph​

Each milestone includes an ASCII dependency graph visualizing blocking relationships:

M##-001 --> M##-002 --> M##-003
                   \--> M##-004
M##-005 --> M##-006
M##-007 (independent)

Legend: A --> B means A blocks B (B is blocked by A)

7. Sub-Issues​

Sub-issues use the Sub-task issue type and are linked via setParentForIssues.

##### Sub-Issues

| ID        | Title           | Type     | Estimate | Labels              |
| --------- | --------------- | -------- | -------- | ------------------- |
| M00-001-a | Sub-issue title | Sub-task | 2        | `Content`, `Python` |

Sub-issues inherit their parent's Epic, Milestone, and Sprint -- these fields are omitted from the sub-issue table.

Convert a subtask to a sub-issue when it is:

  • Independently estimable (could be assigned story points)
  • Independently assignable (different person could do it)
  • Independently testable (has its own acceptance criteria)
  • Substantial (more than a checkbox-level task, typically 2+ story points)

Keep lightweight items as Subtasks (checkbox list within the issue body).

8. MCP Translation Reference​

Every issue metadata field maps to a specific MCP tool call. This table is the agent's translation guide:

Issue FieldMCP ToolParameters
TitlecreateGitHubIssuetitle
Description + AC + NotescreateGitHubIssuebody (markdown)
TypesetIssueTypeissueIds, issueTypeId
Epic (parent)setParentForIssuesparentIssueId, childIssueIds
EstimatesetIssueEstimateissueId, estimate
SprintaddIssuesToSprintsissueIds, sprintIds
PipelinemoveIssueToPipelineissueId, pipelineId
LabelscreateGitHubIssuelabels (array, on create)
DependenciescreateBlockageblockedIssueId, blockingIssueId
Sub-IssuessetParentForIssuesparentIssueId, childIssueIds
Dates (Epics only)setDatesForIssueissueId, startDate, endDate
AssigneesassignIssuesissueIds, assigneeIds
PriorityupdateIssueissueId (via native priority field)

Notes:

  • issueTypeId, pipelineId, sprintId are runtime-resolved via getIssueTypes, getWorkspacePipelinesAndRepositories, getSprint/listRecentSprints
  • repositoryId is resolved via getWorkspacePipelinesAndRepositories
  • Epic IDs are resolved by searching for the epic title after creation
  • Labels are passed as string arrays matching the names defined in section 1

9. Sections to Preserve Unchanged​

The following sections within each milestone file must not be modified during enhancement:

  • Phase Context
  • Prerequisites table
  • Epic / Story Areas table
  • Document References
  • Sprint Mapping
  • Relevant Risks
  • Cross-Cutting Concerns (Testing, Documentation, CI/CD)
  • All Description text
  • All Acceptance Criteria
  • All Technical Notes

10. Summary Statistics​

Each milestone ends with a summary table:

## Summary

| Metric                    | Count  |
| ------------------------- | ------ |
| Total Issues              | N      |
| Sub-Issues                | N      |
| Total Estimate (pts)      | N      |
| Sprints                   | S#--S# |
| Dependencies (blocking)   | N      |
| Dependencies (blocked by) | N      |