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 New Work → Import issues.
What importing does
Imported items do not go straight to an agent. Each one goes through Qualification: duplicates are merged, already-fixed and unverifiable items are stopped, and qualified items become a task or a plan. Anything that needs a decision waits under Factory → Review. See Importing work.
Jira
Both Jira Cloud and Jira Server are supported. Issues import with their type, labels and estimate.
New issues as requests
Coroid can also take new Jira issues as requests. Switch on Jira in Quality Control, under the organization default's Before work starts, in Where requests come from. A new issue is filed for Qualification when its type and priority match what Adjust sets: by default bugs of High priority and above. Adjust lists Jira's standard issue types and priorities (Highest, High, Medium, Low, Lowest, and Blocker, Critical, Major, Minor and Trivial at the same ranks); an issue with a custom priority is filed only when Adjust files every priority. With the switch off, new issues file nothing.
Jira authors are never trusted, so a request from Jira waits for someone to start the work it becomes.
The Jira webhook
New issues reach Coroid only through Coroid's Jira webhook, signed with the webhook secret set up for Coroid. The Jira row says when Coroid has not received anything from your Jira yet. On coroid.ai the Jira webhook is not set up yet, so new issues cannot arrive this way; import Jira issues instead. See Triggers and destinations.
New Work used to offer a "Bring in high-priority Jira bugs" template, a daily schedule that asked Jira through an MCP server. A schedule you created from it keeps running and is named on the Jira row.
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.