[Frontend] Fold the Recording Dashboard and SessionDetail's recording panel into one live-session screen #386

New issue

Closed

opened 2026-08-25 20:42:23 +00:00 by claude-bot · 2 comments

claude-bot commented 2026-08-25 20:42:23 +00:00

Collaborator

Copy link

Impact: MEDIUM

Found in the August 2026 session lifecycle review (#319).

What the user experiences

A GM managing a live session has to juggle three partially-overlapping screens — SessionDetail, RecordingDashboard, and SessionShelf — with incomplete links between them. AudioStatusSection on SessionDetail and the standalone RecordingDashboard show heavily overlapping recording/attendance state with different labels for the same toggle ("Present"/"Absent" on one, "✓ Here"/"Absent" on the other) and different summary affordances (editable on one, read-only on the other, with nothing telling the user editing lives elsewhere). The Recording Dashboard's own entry link is labelled "Dashboard →" — which in a product that already has a page called "Dashboard" reads as "go home", not "recording controls" — and it only appears once a session leaves the proposed state, so a GM cannot even reach recording controls to test them before confirming a time.

Evidence

• webapp/frontend/src/pages/SessionDetail.jsx:110-415 (AudioStatusSection) and webapp/frontend/src/pages/RecordingDashboard.jsx (539 lines) — overlapping state, different labels for the same attendance toggle (SessionDetail.jsx:1385,1404 vs RecordingDashboard.jsx:435).
• webapp/frontend/src/pages/SessionDetail.jsx:317-357 (editable summary) vs webapp/frontend/src/pages/RecordingDashboard.jsx:496-506 (read-only), with no indication on the read-only copy that editing exists elsewhere.
• webapp/frontend/src/pages/SessionDetail.jsx:193-199 — the sole inbound link to the Recording Dashboard, labelled "Dashboard →", GM-only.
• webapp/frontend/src/pages/SessionDetail.jsx:121-122 — showForGm = isGm && ["confirmed","in_progress","completed"].includes(session.status); a session still proposed has no path to the recording dashboard at all.
• No link exists from SessionShelf — the surface a GM actually has open during play — to the Recording Dashboard, or from the campaign page or dashboard.

Why it matters for a hosted product

Three partial screens for one live-session job means a GM has to remember which screen has which control, and the mislabelled "Dashboard →" entry point actively works against discovery in a product that already overloads the word "Dashboard".

Proposed fix

Fold the Recording Dashboard's live-status panel (its strongest feature — SSE stream, elapsed timer, per-speaker capture, "Present, not captured yet") into SessionDetail, or fold SessionDetail's recording panel away in favour of the standalone dashboard — either direction is acceptable, but pick one canonical live-session screen rather than maintaining two. Rename the entry link away from "Dashboard →" regardless of which direction is chosen. Make the recording controls reachable from a proposed session so a GM can test recording ahead of confirming a time. This is the audit's C4.

Acceptance criteria

• There is one canonical screen for live-session recording controls and status, not two with divergent labels for the same data.
• The entry link to that screen is not labelled "Dashboard →".
• Recording controls are reachable for a session in proposed status, not only confirmed/in_progress/completed.
• The attendance toggle uses the same label wherever it appears.

**Impact: MEDIUM** Found in the August 2026 session lifecycle review (#319). ## What the user experiences A GM managing a live session has to juggle three partially-overlapping screens — `SessionDetail`, `RecordingDashboard`, and `SessionShelf` — with incomplete links between them. `AudioStatusSection` on `SessionDetail` and the standalone `RecordingDashboard` show heavily overlapping recording/attendance state with different labels for the same toggle ("Present"/"Absent" on one, "✓ Here"/"Absent" on the other) and different summary affordances (editable on one, read-only on the other, with nothing telling the user editing lives elsewhere). The Recording Dashboard's own entry link is labelled "Dashboard →" — which in a product that already has a page called "Dashboard" reads as "go home", not "recording controls" — and it only appears once a session leaves the `proposed` state, so a GM cannot even reach recording controls to test them before confirming a time. ## Evidence - `webapp/frontend/src/pages/SessionDetail.jsx:110-415` (`AudioStatusSection`) and `webapp/frontend/src/pages/RecordingDashboard.jsx` (539 lines) — overlapping state, different labels for the same attendance toggle (`SessionDetail.jsx:1385,1404` vs `RecordingDashboard.jsx:435`). - `webapp/frontend/src/pages/SessionDetail.jsx:317-357` (editable summary) vs `webapp/frontend/src/pages/RecordingDashboard.jsx:496-506` (read-only), with no indication on the read-only copy that editing exists elsewhere. - `webapp/frontend/src/pages/SessionDetail.jsx:193-199` — the sole inbound link to the Recording Dashboard, labelled "Dashboard →", GM-only. - `webapp/frontend/src/pages/SessionDetail.jsx:121-122` — `showForGm = isGm && ["confirmed","in_progress","completed"].includes(session.status)`; a session still `proposed` has no path to the recording dashboard at all. - No link exists from `SessionShelf` — the surface a GM actually has open during play — to the Recording Dashboard, or from the campaign page or dashboard. ## Why it matters for a hosted product Three partial screens for one live-session job means a GM has to remember which screen has which control, and the mislabelled "Dashboard →" entry point actively works against discovery in a product that already overloads the word "Dashboard". ## Proposed fix Fold the Recording Dashboard's live-status panel (its strongest feature — SSE stream, elapsed timer, per-speaker capture, "Present, not captured yet") into `SessionDetail`, or fold `SessionDetail`'s recording panel away in favour of the standalone dashboard — either direction is acceptable, but pick one canonical live-session screen rather than maintaining two. Rename the entry link away from "Dashboard →" regardless of which direction is chosen. Make the recording controls reachable from a `proposed` session so a GM can test recording ahead of confirming a time. This is the audit's C4. ## Acceptance criteria - [ ] There is one canonical screen for live-session recording controls and status, not two with divergent labels for the same data. - [ ] The entry link to that screen is not labelled "Dashboard →". - [ ] Recording controls are reachable for a session in `proposed` status, not only `confirmed`/`in_progress`/`completed`. - [ ] The attendance toggle uses the same label wherever it appears.

claude-bot added this to the v4.3.0 - Product Surface: Navigation, Attention & Feedback milestone 2026-08-25 20:42:23 +00:00

claude-bot added the

enhancement

frontend

labels 2026-08-25 20:42:23 +00:00

claude-bot referenced this issue 2026-09-06 00:34:01 +00:00

v4.3.0 build order: Product Surface in eight phases #514

claude-bot referenced this issue 2026-09-06 01:45:41 +00:00

[Frontend] Add a persistent nav bar with real destinations #378

claude-bot referenced this issue 2026-09-06 03:11:38 +00:00

[Frontend] Add a persistent nav bar with real destinations #378

claude-bot referenced this issue 2026-09-06 07:42:57 +00:00

v4.3.0 build order: Product Surface in eight phases #514

claude-bot commented 2026-09-06 08:38:56 +00:00

Author

Collaborator

Copy link

Picking this up as v4.3.0 phase 8 (#514), the last item. As recorded on #514, SessionDetail becomes the canonical live-session screen: the Recording Dashboard's live panel (SSE stream, elapsed timer, per-speaker capture, "present, not captured yet", and the connection-lost state #377 just gave it) moves into the session page's recording section as its own component; the old /sessions/:id/recording address redirects there so bookmarks keep working; the "Recording →" link goes away, the shelf gets a link to the panel, the controls are reachable on a proposed session (with a clear reason if the backend refuses to start one), and the attendance toggle gets one label everywhere.

Picking this up as v4.3.0 phase 8 (#514), the last item. As recorded on #514, `SessionDetail` becomes the canonical live-session screen: the Recording Dashboard's live panel (SSE stream, elapsed timer, per-speaker capture, "present, not captured yet", and the connection-lost state #377 just gave it) moves into the session page's recording section as its own component; the old `/sessions/:id/recording` address redirects there so bookmarks keep working; the "Recording →" link goes away, the shelf gets a link to the panel, the controls are reachable on a proposed session (with a clear reason if the backend refuses to start one), and the attendance toggle gets one label everywhere.

claude-bot referenced this issue 2026-09-06 08:54:47 +00:00

v4.3.0 build order: Product Surface in eight phases #514

rbrooks referenced this issue from a commit 2026-09-06 09:13:55 +00:00

feat(webapp): a live recording panel on the session page (#386)

rbrooks referenced this issue from a commit 2026-09-06 09:13:55 +00:00

refactor(webapp): retire the standalone recording page (#386)

rbrooks referenced this issue from a commit 2026-09-06 09:13:55 +00:00

feat(webapp): reach the recording controls from the shelf (#386)

rbrooks referenced this issue from a commit 2026-09-06 09:13:55 +00:00

docs(webapp): changelog for one live-session screen (#386)

rbrooks referenced this issue from a commit 2026-09-06 09:13:55 +00:00

docs(webapp): the guide's retry instruction names a page that exists (#386)

claude-bot commented 2026-09-06 09:13:57 +00:00

Author

Collaborator

Copy link

Done in the #386 PR (auto-merging on green); ships with v4.3.0.

SessionDetail is now the one screen. The Recording Dashboard's live half moved into a new components/RecordingPanel.jsx: the SSE stream with its polling fallback and reconnect, the #377 three-state connection machine (last known state kept, "Connection lost, retrying…" with how stale it is, "Unknown" when the server has never answered), the elapsed clock, per-speaker capture, "Present, not captured yet", the #327 capture tripwire, and Start/Stop with "End session when stopping recording". Extracted rather than inlined because SessionDetail.jsx was already 1,800 lines. The editable summary stays where it was and nothing read-only duplicates it any more.

/sessions/:id/recording is now a redirect to /sessions/:id#recording, kept alongside the other legacy routes so bookmarks and older Discord embeds still land somewhere useful; RecordingDashboard.jsx and its test file are gone, their behaviour and tests moved. The "Recording →" entry link is gone (the panel is right there), and the shelf, the surface a GM has open during play, gained a Recording link straight to the anchor.

On proposed: no backend change was needed. POST /sessions/{id}/record/start gates on get_session_for_gm and nothing else; there has never been a status rule, so the confirmed-only entry link was hiding a capability that already worked, at exactly the moment a GM wants to check the bot can hear the table. The panel is there from proposed onwards and says so. Where a recording genuinely cannot start (the campaign is not connected to a Discord server, which is the backend's own 400), the button is disabled with the reason on the page rather than hidden.

The attendance toggle now reads "Present" / "Absent" in the one place it appears; the "✓ Here" copy went with the dashboard. The roster is also available from in_progress rather than only completed, so the mid-session roster the dashboard carried is not lost.

One thing the move forced: the live status is per Discord guild, not per session. On a page you opened deliberately that did not matter; on every session page of a campaign it does, or tonight's recording would light up last March's session as "Recording in progress". The payload carries the session id it belongs to, so a recording of another session is reported as exactly that and Start is refused rather than offered.

Also removed the frontend's approveAudio wrapper: it called the backend's documented deprecated shim for /approve, and the dashboard's "Approve transcript" button was its only caller; the session page's "Approve summary" is the same action against the non-deprecated endpoint. The shim itself is untouched. One thing to revisit if a deployment ever grows: the panel opens the SSE stream (one Redis pubsub connection) on every GM session-page view; gating it by status reintroduced the visibility holes this issue exists to remove, so it is left ungated, GM-only.

Frontend suite: 64 files / 799 tests passing, eslint clean apart from the pre-existing CampaignDetail.jsx warning, vite build clean.

Done in the #386 PR (auto-merging on green); ships with v4.3.0. `SessionDetail` is now the one screen. The Recording Dashboard's live half moved into a new `components/RecordingPanel.jsx`: the SSE stream with its polling fallback and reconnect, the #377 three-state connection machine (last known state kept, "Connection lost, retrying…" with how stale it is, "Unknown" when the server has never answered), the elapsed clock, per-speaker capture, "Present, not captured yet", the #327 capture tripwire, and Start/Stop with "End session when stopping recording". Extracted rather than inlined because `SessionDetail.jsx` was already 1,800 lines. The editable summary stays where it was and nothing read-only duplicates it any more. `/sessions/:id/recording` is now a redirect to `/sessions/:id#recording`, kept alongside the other legacy routes so bookmarks and older Discord embeds still land somewhere useful; `RecordingDashboard.jsx` and its test file are gone, their behaviour and tests moved. The "Recording →" entry link is gone (the panel is right there), and the shelf, the surface a GM has open during play, gained a **Recording** link straight to the anchor. On `proposed`: no backend change was needed. `POST /sessions/{id}/record/start` gates on `get_session_for_gm` and nothing else; there has never been a status rule, so the confirmed-only entry link was hiding a capability that already worked, at exactly the moment a GM wants to check the bot can hear the table. The panel is there from `proposed` onwards and says so. Where a recording genuinely cannot start (the campaign is not connected to a Discord server, which is the backend's own 400), the button is disabled with the reason on the page rather than hidden. The attendance toggle now reads "Present" / "Absent" in the one place it appears; the "✓ Here" copy went with the dashboard. The roster is also available from `in_progress` rather than only `completed`, so the mid-session roster the dashboard carried is not lost. One thing the move forced: the live status is per Discord *guild*, not per session. On a page you opened deliberately that did not matter; on every session page of a campaign it does, or tonight's recording would light up last March's session as "Recording in progress". The payload carries the session id it belongs to, so a recording of another session is reported as exactly that and Start is refused rather than offered. Also removed the frontend's `approveAudio` wrapper: it called the backend's documented deprecated shim for `/approve`, and the dashboard's "Approve transcript" button was its only caller; the session page's "Approve summary" is the same action against the non-deprecated endpoint. The shim itself is untouched. One thing to revisit if a deployment ever grows: the panel opens the SSE stream (one Redis pubsub connection) on every GM session-page view; gating it by status reintroduced the visibility holes this issue exists to remove, so it is left ungated, GM-only. Frontend suite: 64 files / 799 tests passing, eslint clean apart from the pre-existing `CampaignDetail.jsx` warning, `vite build` clean.

claude-bot referenced this issue from a pull request that will close it, 2026-09-06 09:14:11 +00:00

feat(webapp): one screen for a live session (#386, phase 8 of v4.3.0) #532

claude-bot closed this issue 2026-09-06 09:29:20 +00:00

claude-bot referenced this issue from a commit 2026-09-06 09:29:22 +00:00

Merge PR #532: feat(webapp): one screen for a live session (#386, phase 8 of v4.3.0)

claude-bot referenced this issue 2026-09-06 09:30:26 +00:00

chore(release): v4.3.0 #533

claude-bot referenced this issue 2026-09-06 09:54:06 +00:00

v4.3.0 build order: Product Surface in eight phases #514

claude-bot referenced this issue 2026-09-06 09:54:19 +00:00

v4.3.0 follow-ups: small findings from the build, bundled #534

claude-bot referenced this issue 2026-09-14 03:26:07 +00:00

v4.3.0 follow-ups: small findings from the build, bundled #534

claude-bot referenced this issue 2026-10-02 04:27:34 +00:00

v4.3.0 follow-ups: small findings from the build, bundled #534

claude-bot referenced this issue 2026-10-27 17:38:37 +00:00

[Perf] Recording panel: open its event stream lazily, one per tab #1247

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

feat/1328-fill-it-in

feat/1328-fill-frontend

feat/1328-fill-backend

feat/9-foundry-push

fix/9-foundry-live

feat/9-foundry-push-frontend

renovate/celery-5.x

feat/5-foundry-connect

feat/9-foundry-push-backend

feat/9-foundry-push-module

feat/5-foundry-frontend

feat/5-foundry-backend

feat/5-foundry-module

release/v4.8.0-rc1

docs/d341-convert-draft

feat/958-update-to-version

feat/958-convert-sheet

feat/958-pathbuilder-import-frontend

fix/1360-heading-order

feat/958-pathbuilder-import-backend

feat/11-weekly-digest

feat/1341-auto-update

docs/d332-superseded

chore/1345-names-cleanup

feat/1342-mentioned-pages

feat/1328-recipes

fix/1346-pgdg-key

perf/1247-shared-recording-stream

chore/132-gitleaks-allowlist

release/v4.7.1

spike/foundry-module

release/v4.7.1-rc1

docs/decisions-d332-d337

fix/bot-certifi

chore/release-4.7.0

chore/release-4.7.0-rc4

chore/deps-4.7.0

chore/release-4.7.0-rc3

fix/1280-quote-must-say-it

fix/1257-names-row-squeeze

chore/release-4.7.0-rc2

fix/1245-pg-upgrade-count

chore/release-4.7.0-rc1

feat/1257-names-in-prep

feat/1257-be

feat/1257-fe

feat/1257-rating-fixes

design/1328-fill-it-in

feat/1257-name-splits

fix/1326-redis-503

feat/1280-fact-suggestions

feat/1280-be

feat/1280-fe

design/1280-fact-suggestions

feat/1279-infobox

feat/1279-be

feat/1279-fe

feat/1321-shelf-copies

design/1279-infobox

feat/1243-table-find

feat/1257-who-rated

feat/1243-prep-drawer

feat/1243-sheet-pickers

design/1243-browse-in-place

feat/1315-hotwords-default

feat/1242-system-filters

feat/1257-more-name-styles

feat/506-leg3-hotwords

design/1242-system-filters

fix/1302-packs-polish

feat/1241-rules-library

design/1241-rules-library

feat/1245-postgres-18

integ/4.6.2

fix/1263-map-ui-2

fix/1263-map-server

fix/1263-map-ui-1

fix/1261-editor-link-menu

fix/1229-axe-4.14-name-mismatch

renovate/axllent-mailpit-1.x

renovate/eslint-monorepo

renovate/authlib-1.x

chore/release-4.6.0

chore/release-4.6.0-rc2

fix/460-rc2-screens

fix/460-rc2-server

fix/release-prerelease-exit

chore/release-4.6.0-rc1

feat/125-campaign-templates

feat/126-calendar

feat/1181-pictures-and-files

feat/1190-event-people

integ/4.6.0

feat/1191-line-of-the-night

feat/1200-starter-packs

chore/bot-multidict-and-playwright-group

fix/1202-this-week-answered-count

fix/122-124-leftovers

fix/1178-get-routes-that-write

fix/1203-journeys-check-names

design/125-campaign-templates

feat/126-calendar-engine

design/126-in-world-calendar

fix/1189-cited-stamp-in-range

fix/1189-v4-looser-check

fix/1189-richer-beats

fix/1113-export-bind-lists

fix/1154-release-notes-by-file

chore/release-4.5.0

chore/release-4.5.0-rc12

fix/1135-wiki-markup-as-text

fix/demo-usage-cost-in-window

chore/release-4.5.0-rc11

fix/1121-sheet-consistency

fix/1121-sheet-5e-terms-and-card-hp

copy/1122-busiest-pages

fix/1121-relevant-choices

fix/1121-wiki-create-npc-save-sheet-links

fix/1029-menu-stays-on-screen

docs/prototype-transcript-bin-wording

fix/1023-editor-save-row-back-scroll

fix/1020-search-exact-first

fix/1020-table-prep

fix/1020-shell-wordmark-footer-bell

fix/1020-wiki-article-party

fix/872-admin-kept-until-phone-tables

feat/l13-milestone-level-waiting

fix/1000-1001-bell-older-setup-context

fix/999-pronouns-in-prompts

fix/l19-other-class-feats

fix/1010-transcript-window-ordinary-confirm

docs/d254-d269-decisions

fix/702-member-search

fix/680-transcript-bin

fix/993-unidentified-prompts

fix/841-redis-timeouts

fix/990-binned-not-exported

fix/830-export-prep-shelf

fix/deps-audit-2026-10-01

fix/877-title-reads

fix/798-audio-received-at

build/lane11-17-j7

build/lane11-16-levelup

build/lane11-14-seams

build/lane11-14-seed

build/lane11-15-start

build/lane11-13-old-block-out

fix/980-review-r3

build/lane11-12-block

build/lane11-8-packs

fix/demo-seed-canonical-names

build/lane11-11-hot-half

docs/l11-decisions

build/lane11-7-convert

build/lane11-10-editing

fix/npm-audit-brace-expansion

build/lane11-9-sheet-page

fix/bot-pyjwt

build/lane11-6-content

fix/lane11-rank-names

build/lane11-2b-language

build/lane11-4-js-evaluator

build/lane11-3-server

build/lane11-5a-pf2e

build/lane11-5b-5e

feat/design-admin

build/lane11-2-evaluator

build/lane11-1-sheet-pieces

build/lane11-0-drawing

fix/943-quest-objectives-fk

fix/prepsheet-shelf-flake

fix/945-leftovers

build/demo-gm-copy

fix/901-email-landings

build/lane10-8-journeys

build/demo-seed-lanes-8-10

fix/887-gm-own-confirmation

build/lane9-5-j1-admin

fix/918-audience-click

fix/useasync-overtaken

ci/939-critical-path

test/937-backend-suite-speed

chore/claude-orchestration

fix/924-xp-gm-only

fix/session-stale-poll

docs/decisions-d239-d242

fix/930-pypdf

build/lane8-journeys

build/925-quest-editor

fix/894-private-page-pictures

build/lane8-p4-drafts

build/lane8-p7-map

build/lane8-p6-handouts-rules

fix/wiki-fixture-names

build/lane10-d227-test-usage

fix/rsvp-horizon-test-tuesday

fix/media-volume-owner

build/lane8-p3-editor

fix/912-unidentified-rename

build/lane8-p5-party-quests

build/lane8-handout-takeback

build/lane10-pickers

build/lane8-p2-article

build/lane8-6-map

build/lane10-7b-email-pages

build/lane8-5-handouts

build/lane10-7a-test-the-bot-pages

build/lane8-p1-pages

build/lane8-4-quests

build/lane8-2b-feeds

build/lane8-3-parties

build/lane8-2a-links

build/lane10-5-commands

build/lane9-6-seed

build/lane10-4b-reactions

build/lane9-4d-pages

build/lane9-4c-pages

build/lane10-4a-posts

build/lane10-3-email

fix/891-web-fonts

build/lane9-4b-pages

build/lane10-6-test-the-bot

build/lane10-2-notify-out

build/lane8-1-wiki-text

build/lane9-4a-frame

design/lane10-drawings

fix/j6-budget

fix/j5-phone-flake

fix/869-test-leaks

fix/843-record-start-followups

build/lane7-all

build/lane6-all

build/lane9-b2-server

chore/changelog-fragments

docs/decisions-d218

build/lane9-a-owner-overview

fix/rule-card-level-label

fix/834-retention-semantics

fix/o3c-record-without-announcement

docs/decisions-d179

docs/decisions-d131-d170

fix/851-commit-before-response

build/lane6-j3-seed

build/lane9-b1-d67-identity

fix/841-blocking-loop

build/lane9-c-backups-audit

fix/vote-race-and-start-commit

fix/recording-announcement

fix/proposal-read-leak

fix/last-admin-guard

build/lane6-p4c-planning

build/lane6-p4b-margin

build/lane6-p4a-sheet

build/lane5-j4-seed

build/lane6-base

build/lane7-pages-talk

build/lane5-pages

build/lane7-pages-safety

build/lane7-p3-safety

build/lane7-p2-notify

build/lane6-p3-planning

build/lane6-p2-history

build/lane6-p1b-items

build/lane7-p1-threads

build/lane5-p6-faces

build/lane6-p1a-sheet

build/lane5-p5-find

build/lane5-p4a-board

build/lane5-p4b-scenes

build/lane5-p3-live

build/lane5-base

build/lane5-p2-cards

docs/lane5-decisions

build/review-r2-wide

fix/review-r1

build/lane5-p1-scenes

build/demo-seed

build/lane4-journeys-j5

build/lane4-page-review-b

build/lane4-page-review-a

build/lane4-page-read

build/lane4-journeys

build/lane4-page-sess2

build/lane4-page-sess1

build/lane4-notes

build/lane4-discord-on-approval

build/lane4-scheduling

build/lane4-versions

build/760-session-number

build/lane4-decisions

build/797-erase-no-regenerate

build/test-race-audit

build/lane3-completions

build/794-dark-only

build/796-titles-scroll

build/791-retention-anchor

build/a11y-sweep

build/shell-followups

build/retention-preview

build/753-backup-readback

docs/d91-d93

build/lane3-j1

build/ci-harness-paths-selftest

fix/useauth-test-race

build/ci-harness-paths

build/777-ai-settings-read

build/lane3-settings-c

build/lane3-settings-b

build/lane3-j6

build/lane3-sessionform

build/lane3-settings-a

build/lane3-members

build/lane3-thisweek

build/lane3-story

chore/87-align-python-3.12

v4.8.0-rc1

v4.7.1

v4.7.1-rc1

v4.7.0

v4.7.0-rc4

v4.7.0-rc3

v4.7.0-rc2

v4.7.0-rc1

v4.6.2

v4.6.2-rc4

v4.6.2-rc3

v4.6.2-rc2

v4.6.2-rc1

v4.6.1

v4.6.1-rc1

v4.6.0

v4.6.0-rc2

v4.6.0-rc1

v4.5.3

v4.5.3-rc1

v4.5.2

v4.5.2-rc1

v4.5.1

v4.5.1-rc2

v4.5.1-rc1

v4.5.0

v4.5.0-rc12

v4.5.0-rc11

v4.5.0-rc10

v4.5.0-rc9

v4.5.0-rc8

v4.5.0-rc7

v4.5.0-rc6

v4.5.0-rc5

v4.5.0-rc4

v4.5.0-rc3

v4.5.0-rc2

v4.5.0-rc1

v4.4.1

v4.4.0

v4.3.0

v4.2.3

v4.2.2

v4.2.1

v4.2.0

v4.1.2

v4.1.1

v4.1.0

v4.0.1

v4.0.0

v3.11.4

v3.11.3

v3.11.2

v3.11.1

v3.11.0

v3.10.0

v3.9.1

v3.9.0

v3.8.0

v3.7.0

v3.6.1

v3.6.0

v3.5.0

v3.4.1

v3.4.0

v3.3.0

v3.2.0

v3.1.0

v3.0.0

v2.1.0

v2.0.0

v1.1.0

v1.0.0

v0.12.0

v0.11.0

v0.10.0

v0.9.1

v0.3.3

v0.9.0

v0.8.0

v0.3.2

v0.3.1

v0.3.0

v0.7.0

v0.6.0

v0.5.0

v0.4.0

v0.2.1

v0.2.0

v0.1.1

v0.1.0

Labels

Clear labels   

backend

Issue related to the backend

  

bot

Issue related to the bot

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

frontend

Issue related to the frontend

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

recording

Issue related to the recording system

  

security

Security hardening / vulnerability work

  

wontfix

This won't be fixed

No labels

backend

bot

bug

duplicate

enhancement

frontend

help wanted

invalid

question

recording

security

wontfix

Milestone

Clear milestone

No items

No milestone

v4.3.0 - Product Surface: Navigation, Attention & Feedback

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

rbrooks/Quest-Board#386

No description provided.