Founder of Unitlane Apps
Jonas Nilsson
Jonas Nilsson is the founder of Unitlane Apps in Sweden. He builds Seatwise and RequestOps, and writes about running Jira and a Jira Service Management desk: unused seats and leavers, customer follow-ups, requests waiting on other teams, waiting time versus SLA time, and service reviews.
Articles
- 15 retro formats and when to use each15 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 cringe30 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 itSomeone 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.
- Are Jira guest users free? What counts and what doesn'tJira 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.
- Atlassian unique billable users explainedOne person counts once for Atlassian Guard, collections and Enterprise plans, but once per app on Standard and Premium. A worked example reconciles the numbers.
- Atlassian's October 2026 price rise: what it means for your renewalOld 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.
- Being 85% sure: how confident forecasts work, in plain wordsWhat '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.
- Customer follow-up message templates for Jira Service ManagementEight copyable Jira Service Management messages: ask customers for missing details and files, follow up, give a last call, and brief colleagues internally.
- Customer follow-ups and auto-close in Jira Service ManagementSet 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.
- 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 change the owner of a filter or dashboard in Jira CloudChange 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.
- How to check which groups give Jira accessSee 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.
- 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 find where a Jira group is usedJira 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.
- How to make agile meetings fun without being childishFun 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 pause the SLA while waiting for the customer in Jira Service ManagementAdd 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 play scrum poker: 5 steps for your first roundHow 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.
- How to read the Jira velocity chart, and where it misleadsWhat 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.
- How to remind approvers in Jira Service Management when they don't respondRemind 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 run a sprint retrospective in 45 minutesA 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 see who gave someone Jira access, and whenJira 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.
- How to size a big backlog in 30 minutesA 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.
- How to track a Jira Service Management request that is waiting on a vendorA 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.
- Jira billable users explained: who counts and how to checkWhat 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.
- Jira Service Management evidence handoff templateA 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 HRAn 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.
- Jira's velocity chart and sprint report vs Bunlings Sprint History and Sprint ForecastWhat Jira's built-in velocity chart, sprint report and burndowns do, what Bunlings Sprint History and Sprint Forecast add, and when Jira's own reports are enough.
- JSM Automation vs RequestOps for customer follow-upsCustomer follow-ups built with Jira Service Management Automation and with RequestOps, compared on one scenario, including when native is the better choice.
- Kanban forecasting in Jira: finish dates without story pointsCount 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.
- Monthly service review for Jira Service Management: agenda and templateRun 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.
- Native Jira vs Bunlings for scrum poker and retrosWhat 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 answersHow 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.
- Removed Jira users but the bill didn't go down? Here's whyWhy 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.
- Retro action items that actually get doneWhy 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 JiraHow 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 appsHow 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 youJira 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 meansWhat 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 usesWhy 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.
- Story points, item counts or hours for forecasting in JiraWhich 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.
- Suspend vs remove user access in AtlassianWhen to suspend, remove, deactivate or delete a user in Atlassian Cloud, and what each does to access, billing, groups, data and the way back.
- Team health check-ins in retros: six questions and what to do with the answersHow 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.
- The Jira sprint report explained: burndown, added work and what Done meansHow 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.
- Velocity vs throughput for sprint planning in JiraVelocity 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 apartThe 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.
- Waiting for customer in Jira Service Management: what the status does and how to find stuck requestsWhat 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.
- Waiting time vs SLA time in Jira Service ManagementWhy 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.
- When will this epic or release be done? Forecasting dates in JiraWhat 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.
- Who is this Jira request waiting on? Another team's next stepWhen 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.
- Why are our estimates always wrong? What your own history can tell youEstimates 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.
- Why removing a user from a group did not remove Jira accessTaking 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.
- Why your Jira Service Management agent count is higher than your agentsYour 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.
- Will we finish the sprint? Forecast it from your own history in JiraA 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 numbersHow 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.
Spotted a mistake? Corrections are welcome at support@unitlane.net.