Separate the estimation room from the tracker
A Jira plugin is convenient, but it is not required for good estimation. The tracker can remain the source of tickets while the planning poker room handles the social part of the ritual: private votes, simultaneous reveal, and focused discussion. This separation is useful for teams that pull work from Jira, Linear, GitHub, spreadsheets, or a product doc during the same refinement meeting.
Run a clean five-step loop
Keep the tracker visible, open a shared room, and move one item at a time through a repeatable loop: explain, vote, reveal, discuss, record. The facilitator should avoid batching too many stories into memory. After each reveal, resolve the estimate or capture the reason the item needs more refinement before moving on.
Record less than you think
Most teams do not need a transcript of every planning poker round. They need the final estimate, the open question if there is one, and maybe a short note about the assumption that changed the number. Recording less keeps the session lightweight and reduces the temptation to treat estimation as ceremony for its own sake.
When to bring Jira back into the flow
Bring Jira or another tracker back in when the team has a final number or a clear next action. Paste the estimate, split the issue, update acceptance criteria, or mark the item as needing discovery. The browser room does not replace the backlog. It gives the team a cleaner place to make the estimation decision before the backlog is updated.