# Import Tickets > Brings tickets that already live in GitHub Issues, JIRA Cloud or Notion onto the project's backlog, so agents can run them like any other card. - Area: Desktop, mobile and web - Plans: All plans - Last checked against the product: 2026-09-30 - Web page: https://agentsroom.dev/docs/import-tickets ## What it does Brings tickets that already live in GitHub Issues, JIRA Cloud or Notion 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 " once set up), then **Refresh** on later visits. - To-do column header: **Import one ticket from **, once a source is connected. - On an imported ticket: a source chip ("Imported from : . Open the original.") and **Refresh from **. ## 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) or **Notion** (a database shared with your integration). 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. 3. Choose what to bring in: **Repository**, **State** (Open, Closed, All), **Labels** for GitHub; **Your projects** or a **Query** for JIRA; **Shared databases** for Notion. 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. It lands at the top of To-do without touching your saved query. ## Settings None. The saved query follows the project on your account; the access token is stored encrypted on each machine and is never uploaded. ## 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, JIRA or Notion, even when the ticket ships here. - Each machine connects separately: the query is saved on the account, the token is not. - JIRA attachments, images and documents alike (up to 10 files of 8 MB each, since 2026-09-30), and Notion images 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. ## Common questions - **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 In Progress 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. - **Does closing the ticket here close the issue in JIRA?** No. Nothing is ever written back. - **Why does the phone say my computer must be running?** The token lives on the desktop, so the import runs there. ## Related - [Backlog Task Board](https://agentsroom.dev/docs/backlog-task-board.md): where imported tickets land and run. - [Import Repositories](https://agentsroom.dev/docs/import-repositories.md): cloning GitHub or GitLab repositories, a different feature. - [Start on the ticket in the agent's name](https://agentsroom.dev/docs/ticket-name-autostart.md): an agent named after a tracker key (`ARD-221`) receives that key as its first message, with no import onto the board.