Approving Bunlings
Bunlings: Scrum Poker & Retrospectives for Jira brings sprint estimation and retros into Jira. This page is for the admin who says yes or no.
In short
- No outside servers. It runs on Atlassian's Forge platform and calls nothing else.
- Your Jira's sign-in. There's no new account. People only see what Jira lets them see.
- Written only on a click. Changes are made as the person who clicked, so Jira's History shows their name.
- You choose the spaces. Show it everywhere, or only in the spaces you pick.
What it stores
Everything is in Forge app storage, hosted by Atlassian. Atlassian holds this data in the same location as your Jira.
- Estimation rooms, rounds, votes and notes left with votes, linked to Atlassian account IDs
- Retro cards, groups, votes, actions and lessons
- Sprint snapshots and a summary of finished work per board, for the retro's facts and working-day figures
- Admin and personal settings
It keeps this while the app is installed, so the cards and retros can remember earlier sprints. It stores no email addresses and no passwords.
What it changes in Jira
Nothing happens by itself. Starting a round changes no work item.
- Agree or Save: the estimate goes in the board's estimate field, or the field chosen in the room, with 10 seconds to undo. Sort by size saves the same way, with 30 seconds to undo.
- Hidden search markers: once a saved estimate has stood for 10 seconds, a property on the work item records the value, spread and date. A second one keeps notes left with votes, without names. Retro actions and created items carry one too. They don't show on the work item, and Jira search can use them.
- Add, Split it and retro actions: create work items, with 10 seconds to undo. Split it also links them, ranks them and adds them to the epic and sprint.
- Only if the room chose it: add a label, move to a status, add to a sprint, or add the reason as a comment.
- Notifications: invites and no-meeting reminders go through Jira. If Jira refuses an invite, a comment mentions the people picked.
Each save is a normal Jira edit, so Jira's usual notices may go to watchers.
Each permission, and why
| Permission | Why it's needed |
|---|---|
storage:app | Keeps rooms, votes, retros and settings in the app's own Atlassian storage. |
read:jira-work | Reads work items, their history and attachments, and what the person may do. |
read:jira-user | Shows names and pictures at the table. |
write:jira-work | Creates and edits work items, links, hidden markers, invites, comments and status moves, when someone clicks. |
read:issue:jira-software | Reads a work item's estimate on the board. |
write:issue:jira-software | Saves to the board's estimate field, and ranks split items. |
read:issue-details:jira | Jira needs it alongside the board's work item reads. |
read:board-scope:jira-software | Finds the board and its backlog. |
read:board-scope.admin:jira-software | Reads the board's setup, such as which field holds estimates. Read only. |
read:project:jira | Reads space names and setup. |
read:sprint:jira-software | Reads sprints, their dates and work items. |
read:jql:jira | Runs searches for work items and finished work. |
write:sprint:jira-software | Adds a work item to a sprint, when someone chose that. |
report:personal-data | Tells Atlassian which accounts the app stores, so a closed account's data can be removed. |
Why does it read board "admin" settings?
This permission is read only. It tells the app which field your board uses for estimates, so nobody has to set that up. It changes no board and gives nobody admin rights.
Why can it write to sprints?
It adds a work item to a sprint in two cases: a room chose that after saving, or someone split an item or put a retro action into a sprint. It's written as that person, with their Jira permissions.
Who does the work
A person's reads and every write run as that person, with their Jira permissions. At sprint start, at sprint close and on a five-minute schedule, the app also reads as itself to prepare the retro's facts and finished-work figures. It only reads when it runs as itself.
The Estimate panel on a work item is open to Jira guests in the app's setup. Guest voting hasn't been proven on a live site, so we don't promise it.
Closed accounts
About once a week the app tells Atlassian which accounts it stores. When Atlassian says an account was closed, the app removes that person's data from its storage.
AI
AI Referee is off by default. Only a Jira admin on a paid licence can turn it on, and rooms and retros have their own switch too. It then sends the text on screen, with names, mentions and emails removed, to the AI model Atlassian provides to apps. It never writes to Jira.
If you uninstall
Access ends at once. Atlassian keeps the app's storage for its retention period, then deletes it (Atlassian's storage reference). Your work items, saved estimates and created items stay, because they're ordinary Jira data. The hidden search markers stay on work items too.
Price
Free for up to 10 users. Above that, from $2.00 per user a month, cheaper per user on bigger sites, with a 30-day free trial. Atlassian bills by the users on your Jira site. See the price calculator.
Report a security problem
Email support@unitlane.net with "Security" in the subject. Say which screen is affected and how to reproduce the problem, and leave out customer data. We aim to reply within 1 business day (Monday to Friday, Central European Time). Confirmed problems are fixed with an app update, and affected customers and Atlassian are told when an incident needs it.
Who runs this
Jonas Nilsson, trading as Unitlane. Questions: support@unitlane.net. See the privacy policy, terms, data processing addendum and security and trust.
We don't hold a SOC 2 report for this app, and it isn't Cloud Fortified.