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

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

New issue
Closed
opened 2026-09-06 09:54:18 +00:00 by claude-bot · 5 comments
claude-bot commented 2026-09-06 09:54:18 +00:00
Collaborator
Copy link

Five small findings surfaced while building v4.3.0 (#514), none of which belonged in the issue that found it. Bundled here rather than filed as five issues; split any that grows.

  • Beat Planner is now redundant (#374 / #305). The Session Prep panel carries the same notes editor; the standalone Beat Planner survives as the roomier version. Decide whether to keep it as a leaf under Session Prep or remove it. Deleting a GM's known workspace was out of scope for #374.
  • audio_processing_started_at column (#381). The processing timer anchors on sessions.updated_at because the pipeline records no start time; an unrelated edit resets it, so it can under-report. A dedicated column set when process_audio takes the job would make the timer exact. One migration.
  • One entry-type taxonomy (#396). TYPE_LABELS for wiki entry types exists in four copies (WikiArticle, CampaignStoryline, WikiProposals, and as LORE_TYPE_LABELS in CampaignDetail). Extract to vocabulary.js or a sibling module so the search results and the next rename touch one file.
  • Campaign invite link versus the instance registration gate (#387). An instance with INVITE_CODE set still refuses a brand-new player who follows a campaign /join/<code> link, because the campaign code and the instance code are different secrets and the login return path carries only the former. The GM guide names this; a fix would let a valid campaign invite satisfy the registration gate for that sign-up.
  • The recording panel's SSE stream on every GM session-page view (#386). The panel opens the live stream (one Redis pub/sub connection for its lifetime) whenever a GM views any session page. Gating it by status reintroduced the visibility holes #386 removed, so it is ungated. Negligible at self-hosted scale; revisit (lazy open on scroll-into-view, or a shared per-tab stream) if a deployment grows.
Five small findings surfaced while building v4.3.0 (#514), none of which belonged in the issue that found it. Bundled here rather than filed as five issues; split any that grows. - [ ] **Beat Planner is now redundant** (#374 / #305). The Session Prep panel carries the same notes editor; the standalone Beat Planner survives as the roomier version. Decide whether to keep it as a leaf under Session Prep or remove it. Deleting a GM's known workspace was out of scope for #374. - [ ] **`audio_processing_started_at` column** (#381). The processing timer anchors on `sessions.updated_at` because the pipeline records no start time; an unrelated edit resets it, so it can under-report. A dedicated column set when `process_audio` takes the job would make the timer exact. One migration. - [ ] **One entry-type taxonomy** (#396). `TYPE_LABELS` for wiki entry types exists in four copies (`WikiArticle`, `CampaignStoryline`, `WikiProposals`, and as `LORE_TYPE_LABELS` in `CampaignDetail`). Extract to `vocabulary.js` or a sibling module so the search results and the next rename touch one file. - [ ] **Campaign invite link versus the instance registration gate** (#387). An instance with `INVITE_CODE` set still refuses a brand-new player who follows a campaign `/join/<code>` link, because the campaign code and the instance code are different secrets and the login return path carries only the former. The GM guide names this; a fix would let a valid campaign invite satisfy the registration gate for that sign-up. - [ ] **The recording panel's SSE stream on every GM session-page view** (#386). The panel opens the live stream (one Redis pub/sub connection for its lifetime) whenever a GM views any session page. Gating it by status reintroduced the visibility holes #386 removed, so it is ungated. Negligible at self-hosted scale; revisit (lazy open on scroll-into-view, or a shared per-tab stream) if a deployment grows.
claude-bot commented 2026-09-14 01:58:45 +00:00
Author
Collaborator
Copy link

Picking up two of the five: the audio_processing_started_at column (#381) and the one entry-type taxonomy (#396). Checked first that neither has been done: the column doesn't exist, and the label map now has six copies, not four — WikiNewEntry.jsx and LorePicker.jsx (ENTRY_TYPE_LABELS) have their own too.

The invite-link-vs-registration-gate item is being investigated separately; Beat Planner and the SSE stream stay as they are for now.

Picking up two of the five: the `audio_processing_started_at` column (#381) and the one entry-type taxonomy (#396). Checked first that neither has been done: the column doesn't exist, and the label map now has **six** copies, not four — `WikiNewEntry.jsx` and `LorePicker.jsx` (`ENTRY_TYPE_LABELS`) have their own too. The invite-link-vs-registration-gate item is being investigated separately; Beat Planner and the SSE stream stay as they are for now.
claude-bot commented 2026-09-14 02:29:35 +00:00
Author
Collaborator
Copy link

Progress: two items in review.

  • audio_processing_started_at: #640
  • the entry-type taxonomy: #641

Invite link vs registration gate: investigated, bug confirmed, and wider than described

The item as written is accurate. The campaign code reaches the OIDC callback only inside next_url in the Redis state (routers/auth.py:124-129). The gate (auth.py:204-211) compares invite_code (always "") with INVITE_CODE, and only after the full IdP round trip. The refusal redirects to /auth-error and discards next_url.

It's worse than that, though. bb77ceb removed the invite-code field from the login page ("site-level invite code gate is redundant") but left the backend gate in place. Nothing in the frontend sends invite_code any more. With INVITE_CODE set, every new sign-up is refused, not just ones arriving from a campaign link. The only way in is hand-typing /auth/login?invite_code=…. The refusal text points at a step that no longer exists.

Proposed fix (no migration, no bot-contract change):

  • In login, when next matches the /join/<code> allowlist, store the campaign code in the OIDC state.
  • At the callback, a new user passes the gate if the instance code matches, or if that code resolves to a live, non-archived campaign, checked at callback time.
  • Recommended: add them to that campaign in the same transaction, so every account admitted this way shows up in the issuing GM's member list.

This needs an owner decision first. Any signed-in user can create a campaign and get a reusable, non-expiring invite code. So "a campaign invite satisfies the gate" effectively means any existing user can admit anyone to the instance, and a leaked /join/ link becomes open registration until the GM regenerates it. How much that matters depends on whether the IdP is closed. The options:

  • A. Any valid campaign invite admits.
  • B. Only invites from campaigns with an admin as GM.
  • C. A toggle (setting or env) on top of A.
  • D. Per-invite expiry or usage caps. Needs a migration and UI.
  • E. Accounts created via invite start pending admin approval.
  • Or retire INVITE_CODE entirely, as bb77ceb's message implied.

Adjacent findings:

  • hmac.compare_digest raises on a non-ASCII invite_code inside the callback's try. The user sees "A database error occurred", and the broad except at auth.py:254-258 logs nothing.
  • docs/API.md:119 documents a 403 where the code returns a 302, and docs/ROADMAP-COMPLETED.md:16 says the gate was removed. Both are wrong.
  • The OIDC callback has no tests at all: not the gate, not first-user-admin, not profile refresh.

Leaving this item open pending that decision.

Progress: two items in review. - `audio_processing_started_at`: #640 - the entry-type taxonomy: #641 ## Invite link vs registration gate: investigated, bug confirmed, and wider than described **The item as written is accurate.** The campaign code reaches the OIDC callback only inside `next_url` in the Redis state (`routers/auth.py:124-129`). The gate (`auth.py:204-211`) compares `invite_code` (always `""`) with `INVITE_CODE`, and only after the full IdP round trip. The refusal redirects to `/auth-error` and discards `next_url`. **It's worse than that, though.** bb77ceb removed the invite-code field from the login page ("site-level invite code gate is redundant") but left the backend gate in place. Nothing in the frontend sends `invite_code` any more. **With `INVITE_CODE` set, every new sign-up is refused**, not just ones arriving from a campaign link. The only way in is hand-typing `/auth/login?invite_code=…`. The refusal text points at a step that no longer exists. **Proposed fix (no migration, no bot-contract change):** - In `login`, when `next` matches the `/join/<code>` allowlist, store the campaign code in the OIDC state. - At the callback, a new user passes the gate if the instance code matches, or if that code resolves to a live, non-archived campaign, checked at callback time. - Recommended: add them to that campaign in the same transaction, so every account admitted this way shows up in the issuing GM's member list. **This needs an owner decision first.** Any signed-in user can create a campaign and get a reusable, non-expiring invite code. So "a campaign invite satisfies the gate" effectively means *any existing user can admit anyone to the instance*, and a leaked `/join/` link becomes open registration until the GM regenerates it. How much that matters depends on whether the IdP is closed. The options: - **A.** Any valid campaign invite admits. - **B.** Only invites from campaigns with an admin as GM. - **C.** A toggle (setting or env) on top of A. - **D.** Per-invite expiry or usage caps. Needs a migration and UI. - **E.** Accounts created via invite start pending admin approval. - **Or** retire `INVITE_CODE` entirely, as bb77ceb's message implied. **Adjacent findings:** - `hmac.compare_digest` raises on a non-ASCII `invite_code` inside the callback's `try`. The user sees "A database error occurred", and the broad `except` at `auth.py:254-258` logs nothing. - `docs/API.md:119` documents a 403 where the code returns a 302, and `docs/ROADMAP-COMPLETED.md:16` says the gate was removed. Both are wrong. - The OIDC callback has no tests at all: not the gate, not first-user-admin, not profile refresh. Leaving this item open pending that decision.
claude-bot commented 2026-09-14 03:26:07 +00:00
Author
Collaborator
Copy link

Status of the five items:

  • audio_processing_started_at column (#381): merged in #640.
  • One entry-type taxonomy (#396): merged in #641.
  • Campaign invite link vs the registration gate (#387): moved to #643. The owner chose option D, so invites get expiry, usage limits and per-campaign join approval, and existing codes expire after 7 days. That issue carries the design and the gate fix. The wider hosted-billing context is recorded in #642.
  • Beat Planner redundancy (#374 / #305): not started. Waiting on the v4.5.0 UX direction.
  • Recording panel SSE stream on every GM session view (#386): not started. Explicitly a "revisit if a deployment grows" item, and #642 (hosted) is where that growth would come from.

Leaving this open for the last two.

Status of the five items: - [x] **`audio_processing_started_at` column** (#381): merged in #640. - [x] **One entry-type taxonomy** (#396): merged in #641. - [ ] **Campaign invite link vs the registration gate** (#387): moved to **#643**. The owner chose option D, so invites get expiry, usage limits and per-campaign join approval, and existing codes expire after 7 days. That issue carries the design and the gate fix. The wider hosted-billing context is recorded in **#642**. - [ ] **Beat Planner redundancy** (#374 / #305): not started. Waiting on the v4.5.0 UX direction. - [ ] **Recording panel SSE stream on every GM session view** (#386): not started. Explicitly a "revisit if a deployment grows" item, and #642 (hosted) is where that growth would come from. Leaving this open for the last two.
claude-bot commented 2026-10-02 04:27:34 +00:00
Author
Collaborator
Copy link

Checked each of the five against main (2b077778), 2 October.

  1. Beat Planner redundant (#374/#305): done. The standalone planner is gone (no BeatPlanner anywhere in frontend or backend); pages/prep/Beats.jsx says "the old Beat Planner folds in here, #534".
  2. audio_processing_started_at: done (#640). Column at app/models/session.py, set in routers/bot.py, routers/sessions.py, routers/admin.py; the timer reads it in pages/session/read.js.
  3. One entry-type taxonomy: done (#641). src/entryTypes.js, no local copies left, entryTypes.test.js.
  4. Invite link vs INVITE_CODE gate (#387): moved to #643, which is closed. Not re-verified here.
  5. Recording panel's event stream on every GM session view (#386): partly. It no longer opens on every GM session page: useRecording is used only by RecordingPanel.jsx and GmTable.jsx, and the panel is mounted only on a confirmed or live session. Within those two views it still opens unconditionally: no lazy open, no shared stream per tab. The last word here was "revisit if a deployment grows".

So only item 5 is left, as a deliberate deferral. Leaving this open for the owner to close or keep for that.

Checked each of the five against main (2b077778), 2 October. 1. **Beat Planner redundant (#374/#305): done.** The standalone planner is gone (no `BeatPlanner` anywhere in frontend or backend); `pages/prep/Beats.jsx` says "the old Beat Planner folds in here, #534". 2. **`audio_processing_started_at`: done** (#640). Column at `app/models/session.py`, set in `routers/bot.py`, `routers/sessions.py`, `routers/admin.py`; the timer reads it in `pages/session/read.js`. 3. **One entry-type taxonomy: done** (#641). `src/entryTypes.js`, no local copies left, `entryTypes.test.js`. 4. **Invite link vs INVITE_CODE gate (#387): moved** to #643, which is closed. Not re-verified here. 5. **Recording panel's event stream on every GM session view (#386): partly.** It no longer opens on every GM session page: `useRecording` is used only by `RecordingPanel.jsx` and `GmTable.jsx`, and the panel is mounted only on a confirmed or live session. Within those two views it still opens unconditionally: no lazy open, no shared stream per tab. The last word here was "revisit if a deployment grows". So only item 5 is left, as a deliberate deferral. Leaving this open for the owner to close or keep for that.
claude-bot commented 2026-10-27 17:38:48 +00:00
Author
Collaborator
Copy link

Closing. Items 1 to 4 are done or moved (see the 2 Oct check). Item 5, the recording panel's event stream, is split into #1247 under the hosted-service milestone, since growth is what would make it matter.

Closing. Items 1 to 4 are done or moved (see the 2 Oct check). Item 5, the recording panel's event stream, is split into #1247 under the hosted-service milestone, since growth is what would make it matter.
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
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#534
No description provided.