Articles
Practical guides for Jira teams, sorted by app: estimation and sprint retros (Bunlings), service desk follow-ups and SLAs (RequestOps), and Jira licences and access (Seatwise).
Start here
Six short guides for beginners
- How to play scrum poker: 5 steps for your first round
- Story points explained: Fibonacci, T-shirt sizes and what a 5 means
- Sprint retrospectives in Jira: native options and apps
- Will we finish the sprint? Forecast it from your own history in Jira
- Who is this Jira request waiting on? Another team's next step
- Jira billable users explained: who counts and how to check
Bunlings
For agile teams: estimation, scrum poker and sprint retrospectives
-
How to play scrum poker: 5 steps for your first round How to play scrum poker: what the cards mean, the five steps of a round, what to do when the votes land far apart, and what to do with a 21. -
Being 85% sure: how confident forecasts work, in plain words What '8 in 10' or '85% sure' really means for a sprint or release date, how a forecast is built from your own history, and how to talk about it without a maths lecture. -
How to read the Jira velocity chart, and where it misleads What the grey, green and black marks on Jira's velocity chart mean, how to read it as a range, and five places where it quietly gives the wrong impression. -
Story points, item counts or hours for forecasting in Jira Which unit to forecast with in Jira: story points, a plain count of work items, or hours. What each is good at, how to test them side by side, and how to switch. -
The Jira sprint report explained: burndown, added work and what Done means How to read Jira's sprint report: the burndown lines, the asterisk on added work items, what counts as completed, and what the report cannot tell you. -
When will this epic or release be done? Forecasting dates in Jira What Jira's epic and release burndown show, a by-hand method that gives a range of dates, and how Bunlings Sprint Forecast puts a likely date on epics. -
Will we finish the sprint? Forecast it from your own history in Jira A simple way to answer 'will this sprint fit?' from your last ten sprints, by hand in Jira, and how Bunlings Sprint Forecast does the same replay for you. -
Work added and removed mid-sprint: what it does to your Jira numbers How work that joins or leaves a sprint after it starts changes Jira's velocity chart, burndown and sprint report, and a simple way to keep your numbers honest. -
15 retro formats and when to use each 15 retrospective formats sorted by situation: quick, feelings and improve. What each one asks, and the kind of sprint it fits. -
30 retro icebreakers that aren't cringe 30 sprint retro icebreakers grouped by mood, how to run one in two minutes, and when to skip it. Work-safe and answerable in a few words. -
Anchoring bias in estimation: the first number wins, and how to stop it Someone says 8 and suddenly everyone thinks 8. The estimation anti-patterns behind it, how to spot each one, and how hidden votes fix the worst of them. -
How to estimate without a meeting (and keep the votes honest) Async estimation in Jira for teams across time zones: who votes, a reveal time, and votes hidden until then. The plain Jira way and the app way. -
How to make agile meetings fun without being childish Fun agile meetings keep the humour in the situation, never at a person, and every bit can be turned down. What helps, what grates, and the off switches. -
How to run a sprint retrospective in 45 minutes A 45-minute sprint retrospective agenda with a start time and a finish line for every block: check-in, write, show all, vote, talk, actions, close. -
How to size a big backlog in 30 minutes A 30-minute plan for sizing a long Jira backlog: sort work items into sizes together, talk only about the ones people disagree on, and save the rest to Jira. -
Kanban forecasting in Jira: finish dates without story points Count the work items your team finishes each week, replay those weeks, and answer with a range instead of a date. No story points needed, on any Kanban board. -
Native Jira vs Bunlings for scrum poker and retros What Jira Cloud does on its own for estimation and sprint retros, what Bunlings adds inside Jira, and when native Jira is the better choice. -
Remote and hybrid retros: anonymous cards and honest answers How to run a remote or hybrid retro people answer honestly: write alone, hide cards until everyone is ready, keep names off, and let the call speak first. -
Retro action items that actually get done Why retro action items stall and how to fix it: one owner, one Jira work item, and a look at last time's open actions before you write new ones. - Scrum poker in Jira: how to run a round without leaving Jira How to run scrum poker in Jira: open a room from the sprint, vote in secret, flip the cards together, talk, and save the agreed number to the estimate field.
-
Sprint retrospectives in Jira: native options and apps How to run a sprint retrospective in Jira: the Confluence page and whiteboard Jira offers, a board of work items, and a retro app inside Jira, side by side. - Story point estimation in Jira Cloud: what Jira does, and what it leaves to you Jira Cloud stores an estimate on each work item but has no voting step. How to switch estimation on, the native ways to set story points, and what an estimation app adds.
-
Story points explained: Fibonacci, T-shirt sizes and what a 5 means What story points measure, when Fibonacci or T-shirt sizes fit, and why a 5 only means something once you check how long your own 5s actually took. -
Story Points field missing in Jira? Find the field your board really uses Why the Story Points field is missing on a Jira work item, how team-managed and company-managed spaces differ, and how to find the field your board really uses. -
Team health check-ins in retros: six questions and what to do with the answers How to run a team health check in a sprint retro: six plain statements, a simple scale, how often to ask, and what to do when the answers come back low. - Velocity vs throughput for sprint planning in Jira Velocity adds up estimates per sprint. Throughput counts finished work items per week. What each tells you, when to use which, and how to read both in Jira.
-
Votes 3 and 13: what to do when estimates are far apart The cards flip and one person says 3, another says 13. Talk before you vote again, ask the outliers first, and split the work item if the gap stays. -
Why are our estimates always wrong? What your own history can tell you Estimates drift when nobody checks how long a 5 actually took. Why that happens in Jira, a ten-minute check each sprint, and how to see how long your 5s actually took.
RequestOps
For service desks: follow-ups, waiting on other teams, SLAs and service reviews
-
Who is this Jira request waiting on? Another team's next step When a Jira Service Management request is stuck on another team's task, here's how to find who has the next step, nudge them where they work, and follow up. -
Waiting time vs SLA time in Jira Service Management Why a request can take 28 hours but show 4 hours on the SLA clock, and how to read waiting time and SLA time side by side without drawing the wrong conclusion. -
Customer follow-ups and auto-close in Jira Service Management Set up customer reminders in Jira Service Management that stop when the customer replies, plus a safe auto-close. Step by step with Automation, and an app option. -
Customer follow-up message templates for Jira Service Management Eight copyable Jira Service Management messages: ask customers for missing details and files, follow up, give a last call, and brief colleagues internally. -
Monthly service review for Jira Service Management: agenda and template Run a 30-minute monthly service review in Jira Service Management: which numbers to use, how to read them honestly, and how to leave with owners and dates. -
How to pause the SLA while waiting for the customer in Jira Service Management Add a pause condition to a Jira Service Management SLA so the clock stops while you wait for the customer, and avoid the traps that keep it running or stuck. -
How to remind approvers in Jira Service Management when they don't respond Remind a Jira Service Management approver who has not decided: a scheduled Automation flow that tags them, the traps to avoid, and what to do when they are away. -
How to track a Jira Service Management request that is waiting on a vendor A request is stuck at a supplier or other third party. Track the wait in Jira Service Management with a status, a promised date and a reminder, and see where it stops. -
Waiting for customer in Jira Service Management: what the status does and how to find stuck requests What the Waiting for customer status does in Jira Service Management, what it leaves to you, and a saved search that finds requests stuck in it for days. -
Jira Service Management evidence handoff template A copyable evidence handoff template for Jira Service Management requests, with a filled offboarding example, clear words for gaps and a readback test. -
Jira Service Management offboarding checklist for IT and HR An offboarding checklist for IT and HR in Jira Service Management: who owns each step, where the proof lives, and how to record what nobody could check.
Seatwise
For Jira admins: licences, access and who really costs a seat
-
Are Jira guest users free? What counts and what doesn't Jira guests are free up to 5 per paid user on Standard, Premium and Enterprise. Who qualifies, what guests can do, why paid users can't be converted, and how to add one. -
Do service accounts and app users count as billable in Jira? Service accounts and the bot users apps create don't count toward your Jira user limit. An ordinary account you made for a script does. How to tell them apart. - How to see who gave someone Jira access, and when Jira doesn't keep one 'given by' name. Find the group behind a person's access, then use the Jira and organization audit logs to see when, and where they fall short.
-
Why your Jira Service Management agent count is higher than your agents Your Jira Service Management license count is higher than the people who work on requests? Find every group that gives agent access, including admin groups, and fix it. - Removed Jira users but the bill didn't go down? Here's why Why removing Jira users doesn't lower this month's bill: how maximum quantity billing and annual user tiers work, when the saving shows up, and what to check.
-
How to change the owner of a filter or dashboard in Jira Cloud Change a Jira filter or dashboard owner as an admin, find everything one person owns, and hand a leaver's filters over before the account is deleted. -
Atlassian's October 2026 price rise: what it means for your renewal Old and new Jira Cloud prices from Atlassian's own tables, when the 13 October 2026 rise reaches your bill, and when removing users really lowers it. -
Atlassian unique billable users explained One person counts once for Atlassian Guard, collections and Enterprise plans, but once per app on Standard and Premium. A worked example reconciles the numbers. -
How to check which groups give Jira access See which groups give people access to Jira in Atlassian Administration, which of them one person is in, and why one removal may not end their access. -
Jira billable users explained: who counts and how to check What makes one person billable for Jira Cloud, who doesn't count, and how to check their access, every group behind it, and when removing it changes the bill. -
Suspend vs remove user access in Atlassian When to suspend, remove, deactivate or delete a user in Atlassian Cloud, and what each does to access, billing, groups, data and the way back. -
Why removing a user from a group did not remove Jira access Taking someone out of one group often leaves Jira access in place, or it comes back. Every reason it survives, how to check each one, and how to confirm. -
How to find where a Jira group is used Jira has no single view of where a group is used. Here is every place to check by hand, from permission schemes and space roles to filters and Automation flows.