What are the key technical challenges when migrating custom fields and epics from Basecamp to Jira Software
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What are the key technical challenges when migrating custom fields and epics from Basecamp to Jira Software
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.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Basecamp Jira Software migration custom fields epics data mapping issue hierarchy official documentation Google ↗
Atlassian Jira Cloud CSV import custom fields epic link parent issue hierarchy documentation Google ↗
- Map CSV data to Jira fields | Jira Cloud · support.atlassian.com
- 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
- Import data from a CSV file · support.atlassian.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Basecamp Jira Software migration custom fields epics data mapping issue hierarchy official documentation OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 | |
Atlassian Jira Cloud CSV import custom fields epic link parent issue hierarchy documentation OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 |