If requests already exist in a tracker, import them instead of retyping. Coroid imports from Jira, Linear, Trello and GitHub Issues.
Begin from Work → Import.
Imports do not execute straight away.
Imported items go into the intake queue. Nothing runs until you route them.
This is the most crucial aspect of this feature. A backlog is a wish list containing duplicates, outdated items, things needing a human decision, and items that no one has agreed to build. Directing an autonomous system at it and letting it run would be costly and incorrect.
Routing imported work
You decide what each item becomes, using the same four options as New Work: one executable task, a phased work plan, a report, or a schedule.
The useful test is the same as elsewhere: if the completed work fits into one pull request that a colleague can read in one sitting, it is a task; if it requires several sequential changes, or you want to approve the approach first, it is a plan.
Imported tickets appear smaller than they actually are. A ticket written as a single sentence often describes a week's worth of work, since the person writing it had the breakdown in mind. Read the brief before routing it as a task.
Imported issues produce imperfect specifications
A ticket written for a human colleague usually assumes shared context: an in-person conversation, a mutual understanding of the system, a "you know what I mean".
Coroid converts the imported text into a specification — read it before approving. Imported work is where under-specification most commonly arises, since no one wrote the ticket expecting it to be executed literally.
Keeping the queue orderly
Route or reject items regularly. An intake queue that builds up with unrouted items is simply a backlog with extra steps.