Your Jira project, worked in the room
Connect a room to a Jira project, import its sprints as tasks on the room’s board, and decide sprint by sprint what travels back. Action items from the room’s meeting minutes can land straight in the project backlog.
Jira
Northwind rollout
NW
northwind.atlassian.net
Sprints 3
NW Sprint 14
Both ways · Qik and Jira
NW Sprint 15
One way · Jira to here
Backlog
One way · Jira to here
Meeting action items
Sync action items to backlogOn
Tasks generated in your meeting minutes are synced to the NW backlog.
Assignees carry over when they have a Jira account on this site.
NW Sprint 14
Room board · 5 tasks from Jira
To do2
Billing page redesign
Pricing table copy
In progress2
Webhook retries for partners
Android crash on login
Done1
SSO for Northwind admins
Meetings feed the backlog, the board feeds the agent
Conversational intelligence turns what was said into issues; the sync keeps the room’s persistent shared state and Jira pointing at the same work.
- 01
Action items become backlog issues
Turn on backlog sync and the action items in the room’s AI minutes are created as issues in the project backlog — not in a sprint, so nobody’s current sprint changes shape after a meeting.
- 02
Assignees carry over
An action item assigned to someone keeps that assignee in Jira when the person has a Jira account on the same site.
- 03
Imported issues are room tasks
Issues arrive as tasks on the room’s board, so the AI project manager plans and reports on them alongside the rest of the room’s work.
Two-way when you want it, one-way by default
The integration is built so that connecting a room never surprises the people who work in Jira.
One project per room
An owner or host signs in to Atlassian once and picks the project the room works on; the room shows the project key and site it follows.
Import sprints
Pull in the backlog and any active or future sprint; their issues arrive as tasks on the room’s board and stay up to date as Jira changes.
Per-sprint sync
Every sprint starts one way, Jira to here. Turn on push for a sprint and edits made in the room reach Jira too.
Minutes to backlog
Send a meeting’s action items to the Jira backlog automatically, or by hand from any set of minutes.
Sync a room sprint to Jira
Link a sprint planned in the room to an existing Jira sprint, or create a new sprint in Jira for it.
Governed by your company
Jira is a room integration your company can allow or block, and only owners and hosts can connect, import or disconnect.
You decide what travels, sprint by sprint
Behind the gear on each imported sprint are three switches, and one line that says in plain words what they add up to.
Push changes to Jira
On, edits to the sprint in the room update Jira. Off, edits made here stay here.
Pull changes from Jira
On, edits made in Jira update the sprint in the room. Off, they are ignored.
Let a Jira delete remove the task
Decide whether deleting an issue in Jira deletes its task in the room. It needs pull to be on.
Visible to all, changed by few
Everyone who opens the Jira page can see how a sprint is syncing; only an owner or host can change it.
NW Sprint 15
One way · Jira to here
Push changes to Jira
Edits here stay here
Pull changes from Jira
Edits in Jira update this sprint
Let a Jira delete remove the task
Deleting the issue deletes the task here
Changes travel one way, Jira to here. Edits in Jira arrive; edits here stay in Qik.
Try the switches — this is the same wording the room shows.
One project, two places, the same work
Jira stays the system your engineers live in. The room is where the work is discussed, minuted and planned.
A sprint is imported
The room picks a sprint from the connected project and its issues arrive as tasks.
It is worked in the room
Tasks move across the room’s board, and with push on, the changes reach Jira.
The meeting adds work
The agent writes the minutes, with action items assigned to the people named.
Actions reach the backlog
Action items become issues in the Jira backlog, ready for the next sprint planning.
Who runs on Jira
Standups that reach the backlog
Follow-ups raised in the daily standup become backlog issues automatically, assigned to the engineer who took them.
Planning with the people outside Jira
Import the active sprint into a room where design, sales and support can see the work and discuss it without a Jira seat.
A client’s Jira, your room
Pull the client’s sprint into your room one way, so your team works from it without changing their project until you choose to.
Jira, answered
A room owner or host. They sign in to Atlassian once and pick the project the room works on. Your company can also block the Jira integration entirely.
Not by itself. Every imported sprint starts one way, Jira to the room. Changes travel back to Jira only for sprints where push is turned on.
Into the project backlog, not a sprint. You can turn this on so it happens after every meeting, or send action items by hand from any set of minutes.
A room follows one Jira project at a time. You can disconnect it and connect a different project whenever you need to.
That is your choice per sprint. With pull and deletions on, the task in the room is deleted too; with deletions off, the task stays.
Deploy an AI project manager with Jira
Every agentic room comes with its apps and its AI project manager. Start free, or walk through it with us.