Azure DevOps Canvas Import
Import Azure DevOps Iterations (Sprints) and Work Items directly onto your Forese.ai project canvas for visualization and Monte Carlo simulation.
What You Can Do
Import Iterations/Sprints
Pull entire sprints directly to canvas
Visualize Dependencies
See Predecessor/Successor links
Run Simulations
Monte Carlo analysis on imported data
Estimate Completion
Get confidence-level date ranges
View Work Breakdown
Hierarchical Epic → Feature → Story → Task structure
How to Import
Open Import Dialog
Open your project in the canvas editor, click the Import button in the toolbar, and select Import from Azure DevOps.
Select Azure DevOps Project
Choose the Azure DevOps project from the dropdown. All projects you have access to will be listed.
Choose Import Method
Select By Iteration to import a sprint, or By Work Item IDs to import specific items by their IDs.
Select Iteration (if applicable)
Pick the iteration/sprint from the dropdown. You can preview the work items before importing.
Configure Import Options
Set options like Include Children, Include Dependencies, Story Points to Days ratio, and Position Strategy.
Import to Canvas
Click Import to Canvas and wait for completion. Imported nodes will appear on your canvas.
Import Options
| Option | Description | Default |
|---|---|---|
| Include Children | Import child work items (Tasks under Stories) | On |
| Include Dependencies | Create edges from Predecessor/Successor links | On |
| Story Points to Days | Conversion ratio for duration estimates | 1.0 |
| Position Strategy | Layout algorithm for node placement | Hierarchical |
Work Item Type Mapping
Work Item Types to Node Types
State Mapping
todoin-progressin-progressdoneblockedDuration Estimation
Duration estimates are derived from Azure DevOps fields in the following priority:
Example: 5 Story Points (ratio 1.0)
Best Case: 3.5 days | Most Likely: 5 days | Worst Case: 6.5 days
Recommended Conversion Ratios
~3 days per point. For experienced teams with few blockers.
~5 days per point. Standard velocity assumption.
~8 days per point. For complex projects or new teams.
Dependencies
Predecessor/Successor Links
Azure DevOps Predecessor and Successor links become dependency edges with Finish-to-Start relationships. The predecessor work item becomes the source, and the successor becomes the target.
Related Links
Related work item links can optionally be imported as edges, useful for tracking related work.
Hierarchy Edges
Parent/child relationships create grouping: Epic contains Features, Features contain Stories, Stories contain Tasks.
Running Simulations
Select Nodes
Select all imported nodes, or a specific subset for focused simulation.
Configure Simulation
Set iterations (1,000 - 10,000), enable dependencies for critical path, choose confidence levels (P50, P85, P95).
Review Results
View expected completion date ranges, critical path nodes, and risk analysis for highest variance items.
Pro Tip: See the Monte Carlo simulation guide for detailed instructions on interpreting results and optimizing your project timeline. Learn more
Troubleshooting
"No work items found"
- Check that the iteration has work items assigned
- Verify your permissions in Azure DevOps
- Ensure work items are in the correct area path
Nodes overlapping
- Use hierarchical layout for complex structures
- Manually adjust positions after import
"Missing duration estimates"
- Add Story Points or Effort to work items in Azure DevOps
- Manually edit durations after import
"Circular dependency detected"
- Review Predecessor/Successor links in Azure DevOps
- Remove one link to break the cycle