Getting started

Open any sprint, board or backlog menu in Jira and choose Estimate. Your work items are already in the room.
Send teammates the room link. They sign in with Jira as usual.
Everyone votes. Cards stay hidden until the reveal, then flip together.
Press Agree to save the number to your board's estimate field. It's written as you, with 10 seconds to undo.

For a retro, choose Open sprint retro on the sprint menu. Your sprint retro appears when the sprint starts.

Where to find it after install

Sprint menu: Estimate this sprint, Estimate without a meeting, Open sprint retro
Board menu: Estimate, Estimate without a meeting, Retro
Backlog menu: Estimate backlog
Jira's Apps menu: Bunlings home
A space's page: Bunlings
On a work item: the Estimate panel
On a dashboard: the gadget "Open actions and recent sessions"
Jira settings, Apps: the admin page

Estimating and saving

Agree saves to your board's own estimate field, such as Story Points. Bunlings reads which field from the board's setup, so nobody has to set it. Saved estimates are searchable in Jira.

Anyone who can edit the work item in Jira can save. If you can't edit it, ask a teammate who can: they see the request in the room.

Point at a card to see what your 5s really took on this board, in working days, from your own finished work.

Got a big backlog? Sort it by size together, and add or split work items as you go. Kanban boards vote Fits or Too big, and get a likely finish date from their own recent weeks.

In a meeting room, put the table on the big screen and everyone votes by phone from a QR code. They sign in to your Jira on the phone.

Estimating without a meeting

Choose Estimate without a meeting on the sprint or board menu. Pick who votes and by when. People vote when it suits them, and Jira reminds them the day before.

The cards open at your time, or when the last person has voted. Then you decide what gets saved. Everyone sees the votes waiting for them on Bunlings home.

Sprint retros

The retro opens with facts from the sprint's estimates, such as votes that were far apart. Add a fact as a card, and pin what you learned: next time a similar work item comes up, the lesson is there.

Retro cards stay hidden until someone presses Show all. Actions become work items in two clicks, and open actions come back next time. The recap copies for your manager or Confluence. There are 50 retro formats to pick from.

For Jira admins

Admins find the who-can-do-what list, the space settings and Get help under Jira settings, Apps. You can hide Bunlings in spaces that don't need it.

Bunlings follows each person's Jira theme, light or dark, and works in ten languages.

Your data

Bunlings runs on Atlassian's Forge platform and makes no calls to outside servers. Its data is kept in Forge app storage, hosted by Atlassian, in the same location as your Jira.

What it reads: a person's reads run as that person, so they only see what Jira lets them see.
What it writes: only after someone clicks, and always as the person who clicked, so Jira's History shows their name. Each save is a normal Jira edit, so Jira's usual notices may go to watchers.
Notifications: invites and reminders for a round without a meeting go through Jira.
When you uninstall: Atlassian soft-deletes the app's storage, keeps it for its retention period, then deletes it (Atlassian's data lifecycle page). Your work items, saved estimates and created items stay, because they're ordinary Jira data.

What it does not do

It runs on Jira Cloud only, not on Jira Data Center or Server.
Everyone who votes signs in to your Jira, also on a phone.
Votes and reminders don't go to Slack or Teams. Reminders are Jira notifications.
Retros aren't a free-form whiteboard. Retro cards live in columns.
It makes no scores per person and no team comparisons.
Rooms and retros belong to a board, so your work items need to be on one.

Support

Questions or trouble? Write to support@unitlane.net or use the support page. Partner supported, Monday to Friday, 09:00 to 17:00, Europe/Stockholm.