Coroid imports work from Jira, Linear, Trello and GitHub Issues, so requests that already exist do not have to be retyped.
Configure connections under Settings → Connections, then import from Work → Import.
What importing does
Imported items land in the intake queue. Nothing executes on import — you route each item yourself, choosing whether it becomes one executable task, a phased work plan, a report or a schedule. See Importing work.
Jira
Both Jira Cloud and Jira Server are supported. Issues import with their type, labels and estimate.
Linear
Issues import with their labels and estimates.
Trello
Cards import as work items. Trello carries less structure than the others — no issue type, often no estimate — so the card text is all you have to judge from. Cards with a real description import far better than cards that are just a title.
GitHub Issues
Uses the same connection as your source control. If GitHub is already connected, nothing further is needed.
Imported text makes imperfect specifications
A ticket written for a human assumes shared context — a conversation, a shared mental model, a "you know what I mean". Coroid turns imported text into a specification and executes it literally.
Always read the generated specification on imported work before approving. This is where under-specification shows up most, because nobody wrote the ticket expecting it to be read this way.
One-way
Importing brings work in. It does not write status back to your tracker, so the tracker remains the system of record for what was requested, and Coroid is the system of record for what was built.
Keeping them in sync, where you need that, is a job for hooks reacting to task events.