What happens to our historical sprint data during a Jira to Azure DevOps migration and how can we prevent data loss
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What happens to our historical sprint data during a Jira to Azure DevOps migration and how can we prevent data loss
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Jira to Azure DevOps migration historical sprint data sprint history velocity burndown official documentation Google ↗
Azure DevOps migration Jira sprint history work item migration tool sprint data limitations Google ↗
- Jira to Azure DevOps/TFS work item migration tool · marketplace.visualstudio.com
- jira-azuredevops-migrator/docs/faq.md at master · solidify/jira-azuredevops-migrator · github.com
- Configure and monitor sprint burndown - Azure DevOps · learn.microsoft.com
- View and configure team velocity - Azure DevOps · learn.microsoft.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Jira to Azure DevOps migration historical sprint data sprint history velocity burndown official documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Azure DevOps migration Jira sprint history work item migration tool sprint data limitations OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |