Is there a reliable way to map Basecamp to-do lists directly into Jira epics without losing subtask hierarchies during the data migration?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Is there a reliable way to map Basecamp to-do lists directly into Jira epics without losing subtask hierarchies during the data migration?
3 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 3 queries…
Searches and sources
ChatGPT3 real searches · gpt-6
Basecamp to Jira migration preserve to-do list nested tasks hierarchy Jira epic importer Google ↗
Jira Cloud issue hierarchy epic story subtask import CSV parent field documentation Google ↗
Basecamp API to-do lists todos nested todos documentation Google ↗
- Create work items using the CSV importer | Jira Cloud · support.atlassian.com
- Keep work parent-child relationships during CSV import to Jira Cloud | Jira and Jira Service Management · support.atlassian.com
- GitHub - basecamp/bc-api: API documentation for Basecamp · github.com
- bc-api/sections/todos.md at master · basecamp/bc-api · github.com
- Import data from a CSV file · support.atlassian.com
- Prepare a CSV file for import | Jira Cloud · support.atlassian.com
Queries
3 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Basecamp to Jira migration preserve to-do list nested tasks hierarchy Jira epic importer OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Jira Cloud issue hierarchy epic story subtask import CSV parent field documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Basecamp API to-do lists todos nested todos documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |