Board - Standup Tool settings not effective or persistent

Question

* A couple notes about the settings panel on the Standup tool:

* Density - There does not seem to be any difference between Default or Compact density settings. 
* The setting states are not 'remembered' between sessions, so my speaker order is always shuffled, requiring me to reorder by hand every time.

Numeric Oasis · Answer

The persistence half is already tracked, so that one does not need logging: JRACLOUD-99400, "Save Jira Standup configurations server-side across user sessions and devices", filed 2 September 2026 and sitting at Gathering Interest. The useful part is its Actual Results, which names the cause rather than just the symptom: Standup settings are held in functional cookies instead of server side, so they reset when you switch browser or device, or whenever cache and cookies are cleared.

That gives you something to check today. The workaround recorded on the ticket is to enable functional cookies and leave browser cache and local storage intact. If your browser is set to clear cookies on close, or functional cookies are blocked by a privacy extension or by policy, the reset will happen every single session, which matches what you are seeing. It will still reset when you move to a different browser or machine, because nothing is persisted server side at all.

For the speaker order specifically there is a separate and older request, JRACLOUD-95258, asking for users to be listed in a predictable alphabetical order under Start Standup. Also Gathering Interest. Of the two, JRACLOUD-99400 is the one that would end the manual reordering outright, so a vote and a short comment there describing your daily standup is where the weight goes.

The density observation looks genuinely unreported. We could not find anything on jira.atlassian.com describing Default and Compact rendering identically, and the two nearest tickets, JRACLOUD-97527 and JRACLOUD-97520, are about board view settings rather than Standup. So that is the one worth raising, and it is a clean report to file: screenshots of the same board under both density settings side by side would be enough for triage.

David Day: Appcento · Answer

Both of those are worth logging, and neither is something you can fix from that panel right now. The density toggle and the speaker order are held against the board session rather than saved as a per user preference, which is why they reset when you come back to the board. Practical workaround, treat the order as a start of standup step and set it before you hit start, it takes a couple of seconds once it is habit. If you want it tracked, add your screenshot and the steps to reproduce to the Jira cloud feedback collection so it sits with the other standup reports.