Where requests already exist in a tracker, import them rather than retyping. Coroid imports from Jira, Linear, Trello and GitHub Issues.
Start from Work → Import.
Imports do not execute immediately
Imported items land in the intake queue. Nothing runs until you route it.
This is the most important property of the feature. A backlog is a wish list containing duplicates, stale items, things that need a human decision, and things nobody has agreed to build. Pointing an autonomous system at it and letting it run would be expensive and wrong.
Routing imported work
You choose 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 anywhere else: if the finished work is one pull request a colleague could read in one sitting, it is a task; if it needs several changes in order, or you want to approve the approach first, it is a plan.
Imported tickets skew larger than they look. A ticket written as a single sentence frequently describes a week of work, because the person writing it had the decomposition in their head. Read the brief before routing it as a task.
Imported issues make imperfect specifications
A ticket written for a human colleague usually assumes shared context: an in-person conversation, a shared understanding of the system, a "you know what I mean".
Coroid turns the imported text into a specification — read it before approving. Imported work is where under-specification most often shows up, because nobody wrote the ticket expecting it to be executed literally.
Keeping the queue honest
Route or reject items regularly. An intake queue that accumulates unrouted items is a backlog with extra steps.