rbrooks/Quest-Board
Watch
1
0
Fork
You've already forked Quest-Board
 0
Code Issues 58 Pull requests 7 Projects Releases 76 Packages Wiki Activity Actions

[Backend] Define the ASR provider contract and normalise on word timestamps #350

New issue
Closed
opened 2026-08-25 20:39:13 +00:00 by claude-bot · 3 comments
claude-bot commented 2026-08-25 20:39:13 +00:00
Collaborator
Copy link

Found in the August 2026 session lifecycle review (#319). Core of the provider abstraction; the shape everything else in this milestone depends on.

Why

The backend currently speaks one bespoke dialect to one out-of-repo WhisperX server, whose behaviour it cannot verify — file/speaker zip order, internal VAD, per-file error handling and whether it ever re-labels a speaker are all unknown from inside this repo. That is an unacceptable dependency for a product that must run on self-hosted CPU, self-hosted GPU, or any of several managed APIs without a rewrite.

Proposed contract

The adapter surface, kept deliberately narrow:

  • Submit one job per track, with a caller-supplied track_id passed through and returned. Association is by id, never by ordering.
  • Complete by webhook or poll.
  • Return a normalised result: words: [{text, start_ms, end_ms, confidence}], plus segments derived from words rather than trusted separately.
  • Accept a vocabulary: list[str] input, mapped per provider to keyterms, keyword boosting, or an initial prompt.
  • Declare its constraints — max duration, max bytes, whether it needs chunking, whether it offers word timestamps at all — so the caller owns chunk-and-remap logic rather than each adapter reimplementing it.

Word-level timestamps are the normalisation target because they are the only representation that supports every downstream need — segment rendering, beat evidence citations, and any future interjection-level interleaving — without a second round trip.

Note that speaker identity never comes from the ASR. Quest Board knows it from Discord track ownership, which is a genuine structural advantage: overlapping speech is already separated onto clean per-speaker tracks, so no provider diarization is needed or wanted.

Acceptance criteria

  • An adapter interface exists with submit / poll / normalise, and track_id passthrough
  • Results normalise to word-level timestamps regardless of provider
  • Providers declare max duration, max size, chunking need, and word-timestamp support
  • Chunk-and-remap lives in shared caller code, not per adapter
  • vocabulary maps correctly for at least the local adapter and one managed adapter
  • No adapter can influence speaker attribution
Found in the August 2026 session lifecycle review (#319). Core of the provider abstraction; the shape everything else in this milestone depends on. ## Why The backend currently speaks one bespoke dialect to one out-of-repo WhisperX server, whose behaviour it cannot verify — file/speaker zip order, internal VAD, per-file error handling and whether it ever re-labels a speaker are all unknown from inside this repo. That is an unacceptable dependency for a product that must run on self-hosted CPU, self-hosted GPU, or any of several managed APIs without a rewrite. ## Proposed contract The adapter surface, kept deliberately narrow: - **Submit** one job **per track**, with a caller-supplied `track_id` passed through and returned. Association is by id, never by ordering. - **Complete** by webhook or poll. - **Return** a normalised result: `words: [{text, start_ms, end_ms, confidence}]`, plus segments derived from words rather than trusted separately. - **Accept** a `vocabulary: list[str]` input, mapped per provider to keyterms, keyword boosting, or an initial prompt. - **Declare** its constraints — max duration, max bytes, whether it needs chunking, whether it offers word timestamps at all — so the **caller** owns chunk-and-remap logic rather than each adapter reimplementing it. Word-level timestamps are the normalisation target because they are the only representation that supports every downstream need — segment rendering, beat evidence citations, and any future interjection-level interleaving — without a second round trip. Note that speaker identity never comes from the ASR. Quest Board knows it from Discord track ownership, which is a genuine structural advantage: overlapping speech is already separated onto clean per-speaker tracks, so no provider diarization is needed or wanted. ## Acceptance criteria - [ ] An adapter interface exists with submit / poll / normalise, and `track_id` passthrough - [ ] Results normalise to word-level timestamps regardless of provider - [ ] Providers declare max duration, max size, chunking need, and word-timestamp support - [ ] Chunk-and-remap lives in shared caller code, not per adapter - [ ] `vocabulary` maps correctly for at least the local adapter and one managed adapter - [ ] No adapter can influence speaker attribution
claude-bot commented 2026-09-01 18:48:42 +00:00
Author
Collaborator
Copy link

Picking this up alongside #351 on feat/350-351-provider-contracts — the two contracts land together, since chunk sizing on the LLM side reads a declared window and neither shape is safe to fix in isolation.

Grounding: what the ASR path actually is today

One bespoke dialect, in transcribe_track (audio_service.py:502):

  • Synchronous POST {url}/transcribe, multipart form audio + speaker + optional language. No submit/poll, no webhook.
  • Returns {"segments": [{start, end, text, speaker}], "language"} — segment-level only. There are no word timestamps anywhere in the pipeline.
  • No declared constraints (max duration, max bytes, chunking need).
  • No vocabulary input.

Two things this issue asks for are already true, and should not be rebuilt:

  • Association is already by id, not ordering. transcribe_track sends one file per request and stamps speaker / track_owner_id from the Track object it was handed. The server's speaker echo is read and deliberately discarded — #342 already fixed that, and the comment at :556 says so explicitly. The adapter contract needs to preserve this property, not introduce it.
  • Chunk-and-remap already lives in caller code. compute_speech_spans → transcribe_track_vad → _transcribe_span_resiliently does span cutting and offset remapping above the transport, which is exactly where this issue says it belongs.

The word-timestamp entanglement

The acceptance criterion "results normalise to word-level timestamps regardless of provider" cannot be satisfied while the only implementation is the bundled server, which is segment-only and out of repo. That is #352's work.

Rather than block this issue behind a server change, I am building to the declare-and-degrade design this issue already describes: a provider declares word_timestamps: bool, and the local adapter declares False and synthesises word spans by interpolating across the segment, flagged as degraded. Downstream code reads words either way and does not branch on provider; #358 surfaces the gap to the user. When #352 lands, the local adapter flips the flag and the interpolation stops being reached.

This keeps the criterion honest — normalisation is real, the precision is declared — instead of asserting a word-level guarantee the pipeline cannot currently make.

Async shape

Contract is submit/poll per this issue's spec. The bundled server is synchronous, so its adapter resolves immediately on submit and poll returns the completed result. That keeps a managed async provider (AssemblyAI-shaped) from needing a second code path, without making the local path pay for polling it does not need.

Picking this up alongside #351 on `feat/350-351-provider-contracts` — the two contracts land together, since chunk sizing on the LLM side reads a declared window and neither shape is safe to fix in isolation. ## Grounding: what the ASR path actually is today One bespoke dialect, in `transcribe_track` ([audio_service.py:502](webapp/backend/app/services/audio_service.py#L502)): - **Synchronous** `POST {url}/transcribe`, multipart form `audio` + `speaker` + optional `language`. No submit/poll, no webhook. - Returns `{"segments": [{start, end, text, speaker}], "language"}` — **segment-level only. There are no word timestamps anywhere in the pipeline.** - No declared constraints (max duration, max bytes, chunking need). - No `vocabulary` input. Two things this issue asks for are **already true**, and should not be rebuilt: - **Association is already by id, not ordering.** `transcribe_track` sends one file per request and stamps `speaker` / `track_owner_id` from the `Track` object it was handed. The server's speaker echo is read and deliberately discarded — #342 already fixed that, and the comment at `:556` says so explicitly. The adapter contract needs to *preserve* this property, not introduce it. - **Chunk-and-remap already lives in caller code.** `compute_speech_spans` → `transcribe_track_vad` → `_transcribe_span_resiliently` does span cutting and offset remapping above the transport, which is exactly where this issue says it belongs. ## The word-timestamp entanglement The acceptance criterion *"results normalise to word-level timestamps regardless of provider"* **cannot be satisfied while the only implementation is the bundled server**, which is segment-only and out of repo. That is #352's work. Rather than block this issue behind a server change, I am building to the declare-and-degrade design this issue already describes: a provider **declares** `word_timestamps: bool`, and the local adapter declares `False` and synthesises word spans by interpolating across the segment, flagged as degraded. Downstream code reads words either way and does not branch on provider; #358 surfaces the gap to the user. When #352 lands, the local adapter flips the flag and the interpolation stops being reached. This keeps the criterion honest — normalisation is real, the *precision* is declared — instead of asserting a word-level guarantee the pipeline cannot currently make. ## Async shape Contract is submit/poll per this issue's spec. The bundled server is synchronous, so its adapter resolves immediately on submit and `poll` returns the completed result. That keeps a managed async provider (AssemblyAI-shaped) from needing a second code path, without making the local path pay for polling it does not need.
claude-bot commented 2026-09-01 20:29:37 +00:00
Author
Collaborator
Copy link

Landed in PR #483 (merged, CI green on all 7 jobs). Leaving this open — five of six criteria are met and the sixth genuinely needs a second adapter.

Criteria

  • Adapter interface with submit / poll / normalise, and track_id passthrough — AsrProvider in app/providers/asr.py. Synchronous providers resolve on submit and poll returns what it holds, so an async managed provider needs no second code path.
  • Results normalise to word-level timestamps regardless of provider — with the declare-and-degrade caveat below.
  • Providers declare max duration, max size, chunking need, and word-timestamp support — AsrCapabilities, with needs_chunking derived from the declared limits.
  • Chunk-and-remap lives in shared caller code, not per adapter — was already true; the contract preserves it rather than introducing it.
  • vocabulary maps correctly for at least the local adapter and one managed adapter — local only. LocalWhisperProvider maps it to Whisper's initial_prompt, truncated to a declared 100-term limit. A managed adapter needs #360 to pick one first. transcribe_track carries the parameter through so #355 is a call-site change, not a plumbing one.
  • No adapter can influence speaker attribution — TranscriptionResult has no speaker field. There is a test asserting its absence, so adding one to make an adapter's life easier fails and sends the author to #342.

The word-timestamp caveat, restated now it is real

LocalWhisperProvider declares word_timestamps=False and interpolates spans across each segment by character length — proportional, so "a" and "extraordinarily" do not get equal time — marking every word interpolated=True and the result word_timestamps_interpolated.

Nothing downstream consumes words yet. On this provider they would add no precision over the segments they came from, and pushing a new shape through merge_attributed_transcript and the transcript_segments rows is a change worth making when #352 makes the words real. So the normalisation is in place and unexercised, which is the honest state.

Wiring

transcribe_track now resolves an adapter and submits through it. Wire format is byte-for-byte unchanged and the returned dict shape is unchanged, so transcribe_session, transcribe_track_vad, _transcribe_span_resiliently and the merge are untouched; the VAD path comes along because it delegates here.

Mutation-checked rather than assumed: dropping the segment conversion fails 7 of the 54 transcription tests, and pointing the adapter at a wrong path fails 1. Worth recording that only one of those 54 asserts the request URL — the contract tests cover the adapter directly, but that is a thin spot in the pipeline suite if someone changes the endpoint later.

Landed in PR #483 (merged, CI green on all 7 jobs). **Leaving this open** — five of six criteria are met and the sixth genuinely needs a second adapter. ## Criteria - [x] **Adapter interface with submit / poll / normalise, and `track_id` passthrough** — `AsrProvider` in `app/providers/asr.py`. Synchronous providers resolve on submit and `poll` returns what it holds, so an async managed provider needs no second code path. - [x] **Results normalise to word-level timestamps regardless of provider** — with the declare-and-degrade caveat below. - [x] **Providers declare max duration, max size, chunking need, and word-timestamp support** — `AsrCapabilities`, with `needs_chunking` derived from the declared limits. - [x] **Chunk-and-remap lives in shared caller code, not per adapter** — was already true; the contract preserves it rather than introducing it. - [ ] **`vocabulary` maps correctly for at least the local adapter and one managed adapter** — **local only.** `LocalWhisperProvider` maps it to Whisper's `initial_prompt`, truncated to a declared 100-term limit. A managed adapter needs #360 to pick one first. `transcribe_track` carries the parameter through so #355 is a call-site change, not a plumbing one. - [x] **No adapter can influence speaker attribution** — `TranscriptionResult` has no speaker field. There is a test asserting its *absence*, so adding one to make an adapter's life easier fails and sends the author to #342. ## The word-timestamp caveat, restated now it is real `LocalWhisperProvider` declares `word_timestamps=False` and interpolates spans across each segment by character length — proportional, so "a" and "extraordinarily" do not get equal time — marking every word `interpolated=True` and the result `word_timestamps_interpolated`. **Nothing downstream consumes words yet.** On this provider they would add no precision over the segments they came from, and pushing a new shape through `merge_attributed_transcript` and the `transcript_segments` rows is a change worth making when #352 makes the words real. So the normalisation is in place and unexercised, which is the honest state. ## Wiring `transcribe_track` now resolves an adapter and submits through it. Wire format is byte-for-byte unchanged and the returned dict shape is unchanged, so `transcribe_session`, `transcribe_track_vad`, `_transcribe_span_resiliently` and the merge are untouched; the VAD path comes along because it delegates here. Mutation-checked rather than assumed: dropping the segment conversion fails 7 of the 54 transcription tests, and pointing the adapter at a wrong path fails 1. Worth recording that **only one of those 54 asserts the request URL** — the contract tests cover the adapter directly, but that is a thin spot in the pipeline suite if someone changes the endpoint later.
rbrooks referenced this issue from a commit 2026-09-05 00:11:41 +00:00
chore(release): v4.1.1
claude-bot commented 2026-09-05 03:48:16 +00:00
Author
Collaborator
Copy link

The last open criterion — vocabulary maps correctly for a managed adapter — is met by PR #496 (merged 2026-09-05): OpenAiCompatibleAsrProvider (app/providers/asr_openai.py, registered as openai, serving OpenAI, Groq and any /v1/audio/transcriptions server) maps vocabulary to the prompt field, 40 terms, asserted on the wire by the conformance suite. It also returns real word spans, declares the 25 MiB cap (enforced client-side, with chunk-and-remap staying in the caller), and is selectable explicitly in Admin → Bot Settings.

Recap of the whole issue now that it closes: AsrProvider contract with submit/poll/normalise and track_id passthrough (PR #483); declared limits actually enforced and typed errors (PR #493); a second real adapter so the contract is no longer a description of one implementation (PR #496); and the bundled WhisperX server's API v2 (Rhoving/iac-repo#396) makes the local adapter's word timestamps real rather than interpolated — the client side of that is in flight on #352.

The last open criterion — **`vocabulary` maps correctly for a managed adapter** — is met by **PR #496** (merged 2026-09-05): `OpenAiCompatibleAsrProvider` (`app/providers/asr_openai.py`, registered as `openai`, serving OpenAI, Groq and any `/v1/audio/transcriptions` server) maps vocabulary to the `prompt` field, 40 terms, asserted on the wire by the conformance suite. It also returns real word spans, declares the 25 MiB cap (enforced client-side, with chunk-and-remap staying in the caller), and is selectable explicitly in Admin → Bot Settings. Recap of the whole issue now that it closes: `AsrProvider` contract with submit/poll/normalise and `track_id` passthrough (PR #483); declared limits actually enforced and typed errors (PR #493); a second real adapter so the contract is no longer a description of one implementation (PR #496); and the bundled WhisperX server's API v2 (Rhoving/iac-repo#396) makes the local adapter's word timestamps real rather than interpolated — the client side of that is in flight on #352.
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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#350
No description provided.