Import Tickets

  • Desktop, mobile and web
  • All plans

What it does

Brings tickets that already live in GitHub Issues, GitLab Issues, JIRA Cloud, Notion, Linear, Azure DevOps or YouTrack onto the project's backlog, so agents can run them like any other card. You pick a source, connect it, choose a query, preview the issues and import. Replaying the import later updates the tickets already imported instead of duplicating them. The import is strictly one way: nothing is ever written back to the source tool. A single issue can also be pulled in by its reference, and any imported ticket can be refreshed on its own.

Where to find it

  • Backlog header: Import tickets (tooltip "Import from GitHub", or "Connected to <source>" once set up), then Refresh on later visits.
  • To-do column header: the Import button (cloud download icon), once a source is connected. Its tooltip, Import one ticket from <source>, names every connected source (for example "GitHub Issues, JIRA"); the source logos only appear inside the panel.
  • On an imported ticket: a source chip ("Imported from <source>: <key>. Open the original.") and Refresh from <source>.

How to use it

  1. Click Import tickets and pick the source: GitHub Issues (one repository, filtered by state and labels), JIRA (a JIRA Cloud project or a JQL query) Notion (a database shared with your integration) Linear (the issues of one of your Linear workspaces, assigned to you by default), Azure DevOps (the work items of a project of your organization, or a WIQL query) or GitLab Issues (one project of gitlab.com or of your own instance, filtered by state and labels) or YouTrack (a project of YouTrack Cloud or of your own instance, or any YouTrack search).
  2. Connect it. GitHub: Connect with GitHub CLI if a signed-in gh is detected, or paste a Personal access token with read access. JIRA: Workspace address, Atlassian account email, API token. Notion: create an internal integration, share the database with it, paste the integration secret. Linear: create a personal API key (Linear Settings > Security & access), give the workspace an optional name (for example "Acme") and paste the key. A key opens one workspace: connect each client's workspace with its own key, then Add a workspace from the query screen. Azure DevOps: type your Organization (the name after dev.azure.com/, or paste the full address) and a Personal access token with the "Work Items (Read)" and "Project and Team (Read)" scopes (the Create a personal access token link opens the right page). GitLab: leave GitLab instance empty for gitlab.com or type your self-hosted address, then Connect with GitLab CLI if a signed-in glab is detected, or paste a Personal access token with the read_api scope. It is the same connection as repository cloning and the CI badge, so an account already linked skips this step. YouTrack: type the YouTrack address (for example https://your-company.youtrack.cloud, or your self-hosted address with its /youtrack path if it has one; pasting an issue link works too) and a Permanent token created in your YouTrack profile, under Account Security, with the YouTrack scope.
  3. Choose what to bring in: Repository, State (Open, Closed, All), Labels for GitHub, and the same with a Project for GitLab; Your projects or a Query for JIRA; Shared databases for Notion; for Linear, the Workspace, Assigned to me (checked by default), Teams, Projects (or No project), Status types (To do, In progress, Completed...) and Statuses (the teams' own columns, such as In Review). An empty group means "any". For Azure DevOps, pick one of Your projects (it fills the Query (WIQL) field) or write your own WIQL; add AND [System.AssignedTo] = @Me to keep only your work items. For YouTrack, pick one of Your projects (it fills the Search query field with project: ABC #Unresolved) or type any search that works in YouTrack, a board or sprint filter included; add for: me to keep only your issues. Click Preview.
  4. Tick the issues (Select all, search by key or title) and click Import N tickets. The summary counts tickets created, updated and already up to date.

To replay, click Refresh: title, description, type and labels follow the issue; your assigned agent, notes, board order and links are never touched; a ticket already in progress or done never returns to To-do; an issue that left the query keeps its ticket.

To import one issue, use the To-do column button and paste a reference: owner/repository#42, PROJ-123 or a JIRA URL, a Notion page link, ENG-123 or a linear.app issue link, an Azure DevOps work item number (1234, #1234, AB#1234) or its dev.azure.com link, group/project#42 or a GitLab issue link (/-/issues/42 or /-/work_items/42), ABC-123 or a link to a YouTrack issue of the connected instance. A Linear link names its workspace; with a bare ENG-123 and several workspaces connected, pick the workspace in the panel (or leave Any connected workspace: a key found in two workspaces is refused and the link is asked for instead). It lands at the top of To-do without touching your saved query.

From Odoo, the import works from a file, with no connection: in Odoo, open Project > the project's tasks in list view, select the tasks, then Action > Export, format CSV (keep at least the Title field, or tick the import-compatible export). In AgentsRoom, Import tickets > Odoo (CSV file), choose the file, then preview and import as usual. Importing the same file again updates the tickets instead of duplicating them when the export includes the ID column.

Settings

None of its own. The saved query follows the project on your account; the access token is stored encrypted on each machine and is never uploaded.

The project's New tickets run in a separated worktree (Project settings > Defaults > Git, see Git Worktrees) applies to imported tickets too (since 2026-11-13): a newly imported ticket arrives with Code in a separated worktree for this task ticked, on a branch named after its reference and title (proj-123-fix-login, 42-fix-login), with -2, -3 when another ticket already holds that name. A refresh never changes the worktree settings of a ticket that is already on the board.

Agent tools (MCP)

None. Imported tickets are ordinary backlog tickets, readable with backlog_list and backlog_get.

Providers

All providers, no difference: an imported ticket runs on whatever agent you assign it.

Mobile

Present for the actions that need no token entry: Refresh imported tickets and Import a ticket in the board menu, and refresh from a ticket's sheet. Both run on your computer, so the desktop must be open ("AgentsRoom must be running on your computer: the access token stays there"). Connecting a source or composing a query is desktop only.

Limits

  • Read only: no status change, comment or closure is pushed to GitHub, GitLab, JIRA, Notion, Linear, Azure DevOps or YouTrack, even when the ticket ships here.
  • Each machine connects separately: the query is saved on the account, the token is not. Since 2026-10-06, on a machine without the token the board button turns into Reconnect with an orange "JIRA not connected" badge (the source's name and logo), instead of a harmless "last refreshed" age. For Linear the badge names the workspace: "Linear (Acme) not connected".
  • JIRA attachments, images and documents alike (up to 10 files of 8 MB each, since 2026-09-30), Notion images, Linear uploaded images and files (up to 10 per issue), and Azure DevOps attachments and pasted screenshots (up to 10 per work item) are downloaded and attached to the ticket; GitHub bodies keep their public image URLs as Markdown.
  • An empty JIRA project list usually means a scoped API token, which that endpoint treats as anonymous.
  • A Notion integration sees nothing until you share the database with it.
  • Linear: up to 300 issues per import. Priority, estimate, team, project, cycle, parent and sub-issues are written at the end of the description as context for the agent; sub-issues are listed, not imported as separate tickets.
  • Azure DevOps (since 2026-10-26): Azure DevOps Services (dev.azure.com) only, Azure DevOps Server installed on premises is not supported. One organization per computer: to import from another one, disconnect and connect it. Up to 500 work items per import. Description, repro steps and acceptance criteria are imported; type, state, area, iteration, priority, story points and parent are written at the end of the description. A work item counts as done when its state belongs to the Completed category, whatever its name (Done, Closed, Resolved). Comments, the assignee and links between work items are not imported.
  • GitLab (since 2026-11-02): one instance per computer, gitlab.com or self-hosted; to import from another one, disconnect and connect it. Up to 500 issues per import. A project that imports from a self-hosted instance shows "GitLab (your.host) not connected" on a machine connected to no instance or to another one. The description is imported as written; milestone, assignees, due date and weight are written at the end of it. The type comes from the labels (bug, type::bug, kind::feature), then from incidents and test cases. Images and files dropped into an issue (up to 10) are attached from GitLab 17.4 on; on an older instance, only those of public projects, and their link stays in the description. Comments are not imported.
  • YouTrack (since 2026-11-12): YouTrack Cloud or self-hosted, one instance per computer; to import from another one, disconnect and connect it. Up to 500 issues per import. The description is imported as written; the issue fields (State, Priority, Assignee, Type...) are written at the end of it. The ticket type comes from the Type field (Bug, Feature, Task, Cosmetics, Exception, Performance Problem...), and the original type is kept as a tag. An issue counts as done when YouTrack marks it resolved. Files attached to the issue (up to 10, 8 MB each) are attached to the ticket. Comments and links between issues are not imported. An http:// address that is not on your computer or your private network asks for a confirmation before connecting, because the permanent token would travel unencrypted; localhost and private addresses (such as 192.168.x.x) connect without asking. Prefer the https:// address of your instance when it has one.
  • Odoo (since 2026-11-16): a CSV file exported from Odoo Project, up to 5 MB and 500 tasks; XLSX files are not read yet, export in CSV. No Odoo server is contacted and nothing is asked for. Title, description (as plain text), tags, and a context block with project, stage, assignees, priority and deadline. A task whose stage is Done, Cancelled or Closed counts as done. Column names are read from the import-compatible export (any language) or from the default English export. No Refresh and no per-ticket refresh: import a new export instead. Attachments and comments are not imported.

Common questions

  • My imported board stopped updating on my second computer. The import query follows the project, but the token stays on the machine that connected it. If the button reads Reconnect with "<source> not connected", click it and connect that source again on this machine.
  • Will running the import twice create duplicates? No. Matching tickets are updated, never duplicated.
  • An imported ticket has no agent and no model, how do I pick them? From the card itself: an imported ticket in TODO or Development always shows its agent and model controls, even on a board that otherwise hides them (fixed on 2026-09-30).
  • I only want the one issue I was just assigned. Use the To-do column button and paste its reference.
  • The To-do column button showed only one tool's logo although I connected several. Before 2026-10-08 that button only showed the logo of the first connected source. It now reads Import with a neutral icon, and its tooltip lists every connected source.
  • Does closing the ticket here close the issue in JIRA? No. Nothing is ever written back.
  • I work for several clients, each with its own Linear workspace. Connect each one with its own API key and a name. The import screen has a Workspace selector, and each project remembers the workspace its import uses.
  • Can I import user stories, bugs and tasks from Azure DevOps? Yes, since 2026-10-26: Import tickets > Azure DevOps, with your organization name and a read-only personal access token. Every work item type comes in; Bug becomes a bug ticket, User Story, Product Backlog Item and Feature become feature tickets, and the original type is kept as a tag.
  • Can I import issues from YouTrack? Yes, since 2026-11-12: Import tickets > YouTrack, with the address of your YouTrack (Cloud or self-hosted) and a permanent token. Choose a project or type a YouTrack search such as project: ABC #Unresolved for: me; a single issue comes in by its ID (ABC-123) or its link from the To-do column.
  • Azure DevOps says my token is not accepted. Check that the token belongs to the organization you typed, has not expired, and has the "Work Items (Read)" and "Project and Team (Read)" scopes.
  • Does GitLab Issues replace the AgentsRoom board, or sync both ways? No. Like every source, GitLab is a one-way import: the board reads issues and updates its tickets when you refresh, and status changes or comments made in AgentsRoom never reach the issue. Replay the import to keep the board in step, and close the issue in GitLab yourself or ask an agent to do it through GitLab's own tools.
  • Can I import tasks from Odoo? Yes, since 2026-11-16, from a file: export the tasks from Odoo Project in CSV format, then Import tickets > Odoo (CSV file). Nothing connects to your Odoo server.
  • Can I import issues from my self-hosted GitLab? Yes. Type its address in GitLab instance when connecting. Your token needs the read_api scope.
  • GitLab says "Access forbidden, check the token scopes". The token was probably created for cloning only (read_repository). Create one with read_api, disconnect, then connect again.
  • Why does the phone say my computer must be running? The token lives on the desktop, so the import runs there.