Area Paths & Component Mapping

The Structural Difference

ADO Area Paths are hierarchical and typically represent team or product structure:

MyProject
  ├── Frontend
  │     ├── React
  │     │     ├── Forms
  │     │     └── Data Grid
  │     └── CSS / Design System
  ├── Backend
  │     ├── API
  │     └── Database
  └── Infrastructure
        ├── AWS
        └── CI/CD

Jira Components are flat — a project has a list of named components with no nesting. An issue can be assigned to one component.

Mapping Approach

During Phase 5, Migrayt shows you the ADO area tree and your existing Jira components. For each ADO area path node, the AI suggests one of four actions:

Which nodes get mapped

Migrayt maps leaf nodes (nodes with no children) by default, because these are the most specific and most useful as Jira components.

For parent nodes (e.g. Frontend), you can choose to:

• Map it to a component of the same name (and have both Frontend and React as separate components)
• Drop it and rely only on the leaf components
• Collapse it so that items under Frontend > React > Forms get the component Frontend

Pre-creation

Any Jira components that need to be created are created before work items are migrated, using a batch API call. Component names and (optionally) descriptions are populated from the ADO area path names.

Component Assignment Per Item

Each ADO work item has a single System.AreaPath field (e.g. MyProject\Frontend\React\Forms). Migrayt resolves the component assignment by:

1. Looking up the full area path in the mapping table
2. If a mapping exists at this exact path → use that component
3. If no mapping exists at this path → walk up the parent chain until a mapping is found
4. If no mapping exists at any level → item is created without a component assignment

Jira only supports one component per issue. If your ADO items are assigned to multiple area paths, only the primary area path is used.

Example

ADO Area Path                    Items   AI Suggestion                        Confidence
──────────────────────────────   ──────  ───────────────────────────────────  ──────────
MyProject\Frontend                  5    Create "Frontend"                    Medium
MyProject\Frontend\React           18    Create "React"                       High
MyProject\Frontend\React\Forms      6    Map to parent → "React"              Medium
MyProject\Frontend\CSS              9    Create "CSS Design System"           High
MyProject\Backend                   3    Drop (only 3 items — use children)   Low
MyProject\Backend\API              44    Create "API"                         High
MyProject\Backend\Database         22    Create "Database"                    High
MyProject\Infrastructure           11    Create "Infrastructure"              High

Labels as Area Path Fallback

For items whose area path has no component mapping, the full ADO area path is preserved as a Jira label in the format ado-area:{last-segment}. For example, MyProject\Frontend\React\Forms becomes the label ado-area:Forms. This ensures no area path information is silently lost.