Documentation

Getting started

1. A Jira admin installs Standup Arcade from the Atlassian Marketplace. It works with Jira Software boards in Jira Cloud.
2. Open a project that has a board. A Standup tab appears in the project's navigation.
3. The first time you open it, Jira may ask you to allow Standup Arcade to act on your behalf. Accept and reload. This is what lets the app read the board with your own permissions and nothing more.
4. The board you see is the project's board; if the project has several, pick one with the board name in the bar. The queue is the people assigned to the active sprint's issues.

Running the standup

The bar above the board shows the board, the sprint, and who is speaking. Under it, the queue: one seat per person, in speaking order.

• Shuffle draws a new order before you start (with fun modes off, the order is visible; with them on, it stays hidden until each person is drawn).
• Start begins the meeting. With fun modes on, a short scene plays and picks the first speaker.
• Next ends the current turn and hands the floor to the next person. Skip moves on without marking the person as having spoken. Back returns to the previous speaker.
• Stop abandons the standup; nothing is recorded. Finish (the last turn) records it.
• Whole team / Current speaker toggles whether the board shows every issue or only the speaker's.
• The drawer under the bar lists everyone as Done, Current, Waiting or Skipped. Click a name under Done or Skipped to jump back to that person.
• Issue cards are live: open one in Jira's own dialog, or move it to another column by dragging. Moves happen with your permissions and go through Jira's normal workflow.
• Full screen (the ⛶ button) keeps the bar and queue in view on a meeting-room screen.

Fun modes

A fun mode is a short animated scene that picks the next speaker: a claw machine, a UFO, a pinball table, a roller coaster and thirteen more. Every scene ends by itself and reveals the speaker; press Esc or click outside it to skip.

• Pick a mode in Settings → Fun mode, or Auto to get a different one each standup, or Off for a plain meeting.
• Fun modes play in the Taskman Arcade theme. In Classic there are no scenes.
• Scenes use your teammates' Jira avatars. A person with no avatar is drawn with their initials.
• Sound is on by default and can be switched off per board.

Settings

Settings belong to the board, not to a person: a standup is one shared screen, so the whole team sees one configuration. Anyone who can open the Standup tab can change them, including who is in the rotation.

• Theme — Taskman Arcade or Classic.
• Fun mode — a scene, Auto, or Off.
• Sound, Hide empty columns, Praises (a short toast after each turn).
• Speaker limits — a soft limit that shows the clock as over time, and a hard limit that moves the standup on. In seconds; 0 means no limit.
• Excluded people — in the drawer before a standup starts, click a name to leave that person out of the rotation, or to bring them back.

History and reports

Every finished standup is kept per board: who spoke, in what order, who was skipped, and how long each turn took. Open History in the bar. The report shows average speaking time per person and how often each person goes first; it says so plainly when there are too few standups for the order figures to mean anything.

Keyboard

• Esc skips a scene, and closes the settings.
• Every control in the bar is a button and can be reached with Tab.

Data and permissions

• Standup Arcade runs entirely on Atlassian's Forge platform, inside your Atlassian site. It has no servers of its own and makes no outbound requests; it is eligible for Atlassian's Runs on Atlassian designation.
• It reads Jira as the person using it, so everyone sees exactly what they may already see in Jira — including issue-level security.
• It stores, in your site's own Forge storage: per-board settings, and for each finished standup the Atlassian account IDs of the participants with their order, status and speaking time. Never names, emails, avatars or issue content.
• Once a week it reports the account IDs it holds to Atlassian's privacy API; a closed account is erased from every standup and exclusion list within that cycle.
• Details: the Privacy Policy and the security policy.

Known limits

• The queue is built from the assignees of the active sprint's issues — or, when the board has no active sprint, of the board's issues. Unassigned issues add nobody.
• A person who asks to be forgotten while their Atlassian account stays open is not erased automatically yet — write to privacy@lukany.co.
• Under a full-screen scene, the controls beneath it are still reachable by keyboard. We know; it is on the list.

Something else? Support is one email away.