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

[UX] Inventory every surface and define the redesign brief #361

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

Found in the August 2026 session lifecycle review (#319). First step of the total UX overhaul — nothing else in this milestone starts until this exists.

Why

The review found the product has no navigational spine and no attention surface: one badge in the entire web app, one of thirteen Discord embeds linking back to it, and every high-value surface reachable by exactly one small link buried inside another page. Those are structural problems being fixed in v4.3.0. This milestone is the visual and interaction redesign that sits on top.

A redesign needs a brief, and the brief needs an honest inventory. The review already produced most of it.

What to produce

  • The surface inventory — every route, what it is for, who it is for, and how it is reached today. Review E's §2.1 route table is the starting point and includes the click-depth from the dashboard and whether each route is reachable without typing a URL.
  • The journeys that must work, from review E §3: GM first campaign; players notified → vote → RSVP → see the confirmed session; GM prepping; live session; after-session review and approval; player finding the recap.
  • The naming decisions, from review E §7.1. One concept currently has up to eight names — prep alone is planning / CampaignPlanning / GM Workbench / Session Prep / Session Prep Sheet / Beat Planner / beat notes / Session Shelf. The redesign must ship one vocabulary, and it should be settled in the brief rather than argued during implementation.
  • The constraints: the product is used live at a table, often on a phone or tablet; it serves two clearly distinct roles (GM and player) with very different needs; and it must remain usable by a group that is not Discord-native.
  • What is already good and should survive — review E §4.3 lists these, including the live recording panel, the four-stage lore status labelling, and the campaign-vs-viewer timezone display. A redesign that loses these is a regression.

Acceptance criteria

  • Complete surface inventory with purpose, audience, and current entry points
  • The six core journeys documented as the acceptance bar for any design
  • One vocabulary decided, with the mapping from every current name
  • Explicit list of existing behaviours that must be preserved
  • Brief is written down and agreed before wireframing begins
Found in the August 2026 session lifecycle review (#319). First step of the total UX overhaul — nothing else in this milestone starts until this exists. ## Why The review found the product has **no navigational spine and no attention surface**: one badge in the entire web app, one of thirteen Discord embeds linking back to it, and every high-value surface reachable by exactly one small link buried inside another page. Those are structural problems being fixed in v4.3.0. This milestone is the visual and interaction redesign that sits on top. A redesign needs a brief, and the brief needs an honest inventory. The review already produced most of it. ## What to produce - **The surface inventory** — every route, what it is for, who it is for, and how it is reached today. Review E's §2.1 route table is the starting point and includes the click-depth from the dashboard and whether each route is reachable without typing a URL. - **The journeys that must work**, from review E §3: GM first campaign; players notified → vote → RSVP → see the confirmed session; GM prepping; live session; after-session review and approval; player finding the recap. - **The naming decisions**, from review E §7.1. One concept currently has up to eight names — prep alone is *planning / CampaignPlanning / GM Workbench / Session Prep / Session Prep Sheet / Beat Planner / beat notes / Session Shelf*. The redesign must ship one vocabulary, and it should be settled in the brief rather than argued during implementation. - **The constraints**: the product is used live at a table, often on a phone or tablet; it serves two clearly distinct roles (GM and player) with very different needs; and it must remain usable by a group that is not Discord-native. - **What is already good and should survive** — review E §4.3 lists these, including the live recording panel, the four-stage lore status labelling, and the campaign-vs-viewer timezone display. A redesign that loses these is a regression. ## Acceptance criteria - [ ] Complete surface inventory with purpose, audience, and current entry points - [ ] The six core journeys documented as the acceptance bar for any design - [ ] One vocabulary decided, with the mapping from every current name - [ ] Explicit list of existing behaviours that must be preserved - [ ] Brief is written down and agreed before wireframing begins
claude-bot commented 2026-09-06 19:45:57 +00:00
Author
Collaborator
Copy link

Picking this up (build order in #535). Two facts about the inputs, for the record:

  • The audit's review E is gone. docs/.internal/ is gitignored and the session-review folder exists on no machine or server I can reach, so the §2.1 route table, §3 journeys, §4.3 "already good" list and §7.1 naming cannot be quoted. Their substance survives in the v4.3.0 issue bodies (#368–#396), which were written from them and are now closed with completion notes; the naming decisions shipped in #379 as vocabulary.js.
  • A fresh inventory replaces the route table. v4.3.0 changed navigation enough (nav bar, redirects, new public routes) that the August table would have been wrong anyway. The new one covers every route (purpose, audience, entry points, click depth, size), the DOM order of every page, the responsive facts, the duplicated-concept list, and a visual baseline with counts. Headline measurements: the Shelf's six header controls vanish below sm with no substitute; 100 of 130 status classes are hard-coded dark; 87 inline copies of the primary button and 60 of the card; six copies of the wiki type labels; 39 confirm() and one alert(); seven routes three or more clicks deep; no typeface, no icon set, no progress indicator anywhere.

The brief (journeys, constraints, must-survive, the five vocabulary leftovers with recommendations, the inventory) is being presented together with the #362 concepts as one review page, so there is one checkpoint rather than two. It gets committed under docs/ once agreed.

Picking this up (build order in #535). Two facts about the inputs, for the record: - **The audit's review E is gone.** `docs/.internal/` is gitignored and the session-review folder exists on no machine or server I can reach, so the §2.1 route table, §3 journeys, §4.3 "already good" list and §7.1 naming cannot be quoted. Their substance survives in the v4.3.0 issue bodies (#368–#396), which were written from them and are now closed with completion notes; the naming decisions shipped in #379 as `vocabulary.js`. - **A fresh inventory replaces the route table.** v4.3.0 changed navigation enough (nav bar, redirects, new public routes) that the August table would have been wrong anyway. The new one covers every route (purpose, audience, entry points, click depth, size), the DOM order of every page, the responsive facts, the duplicated-concept list, and a visual baseline with counts. Headline measurements: the Shelf's six header controls vanish below `sm` with no substitute; 100 of 130 status classes are hard-coded dark; 87 inline copies of the primary button and 60 of the card; six copies of the wiki type labels; 39 `confirm()` and one `alert()`; seven routes three or more clicks deep; no typeface, no icon set, no progress indicator anywhere. The brief (journeys, constraints, must-survive, the five vocabulary leftovers with recommendations, the inventory) is being presented together with the #362 concepts as one review page, so there is one checkpoint rather than two. It gets committed under `docs/` once agreed.
claude-bot commented 2026-09-06 20:01:59 +00:00
Author
Collaborator
Copy link

The brief is presented for agreement as the first section of the checkpoint A page: https://claude.ai/code/artifact/6e06cfa2-41fb-4f9b-8ed2-1d4d2f891bfe — the lifecycle strip, the six journeys as the acceptance bar, what is wrong today (nine measured findings), the constraints, what must survive, the five vocabulary leftovers with a recommendation each (Shelf vs Table; fold the Beat Planner; Story / Recap and retire "Journal" from labels; "prep sheet" vs "notes"; one entry-type taxonomy), and the full route inventory behind a disclosure. It is committed under docs/ as v4.4.0-brief.md once agreed, with the checkpoint decisions written into it.

The brief is presented for agreement as the first section of the checkpoint A page: https://claude.ai/code/artifact/6e06cfa2-41fb-4f9b-8ed2-1d4d2f891bfe — the lifecycle strip, the six journeys as the acceptance bar, what is wrong today (nine measured findings), the constraints, what must survive, the five vocabulary leftovers with a recommendation each (Shelf vs Table; fold the Beat Planner; Story / Recap and retire "Journal" from labels; "prep sheet" vs "notes"; one entry-type taxonomy), and the full route inventory behind a disclosure. It is committed under `docs/` as `v4.4.0-brief.md` once agreed, with the checkpoint decisions written into it.
claude-bot commented 2026-09-06 22:22:42 +00:00
Author
Collaborator
Copy link

Brief amended at checkpoint A: a new constraint, the table may be in one room. The live surfaces need a shared-screen face readable at distance and driven from the GM's device; the recording surface must not assume Discord voice is its only source; and no step of play may require every player to hold a device. The in-person features come later (#542); the seams are designed now. Every concept now states where its shared screen lives, and the players' page draws that face for each.

Brief amended at checkpoint A: a new constraint, **the table may be in one room**. The live surfaces need a shared-screen face readable at distance and driven from the GM's device; the recording surface must not assume Discord voice is its only source; and no step of play may require every player to hold a device. The in-person features come later (#542); the seams are designed now. Every concept now states where its shared screen lives, and the players' page draws that face for each.
claude-bot commented 2026-09-21 19:08:44 +00:00
Author
Collaborator
Copy link

The brief is written: docs/design/v4.5.0-brief.md (PR on docs/redesign-brief; merges on green).

It takes the checkpoint A brief (the lifecycle, the six journeys, what was wrong, the constraints, what must survive, the vocabulary leftovers) and carries it through everything decided since: Book & Table and the six shell decisions (#363, #656), Lapis Table, and every decision D1 to D73 from the mockup round (#659), each in a line or two by area with its surfaces. It adds what the design system must provide (#364) and the build lanes in order with the server changes each needs (#366).

Against this issue's acceptance criteria:

  • Surface inventory — the catalogue (#657): 1,672 rows on 107 surfaces, with the route inventory of v4.4.0-concepts/surface-inventory.md behind it. The brief points at both.
  • The six journeys as the acceptance bar — §2, unchanged from checkpoint A, now stated for both roles, desktop and phone, keyboard and touch.
  • One vocabulary, with the mapping from every current name — §5: the five leftovers settled (D38, D47, lane 6b's taxonomy, Shelf/Table), plus every name the redesign introduces, mapped from what it is called today.
  • Existing behaviours that must be preserved — §4, with the two that changed shape (one time rather than two, D17; the checklist as the GM's, D28) said as such.
  • Written down and agreed before wireframing begins — written; wireframing and mockups are done; this is the point to read it and say "agreed", after which this issue closes and #364 can start.

The catalogue's decisions table stays the authority; the brief is its readable synthesis, and a change to a decision is made there first.

**The brief is written: `docs/design/v4.5.0-brief.md`** (PR on `docs/redesign-brief`; merges on green). It takes the checkpoint A brief (the lifecycle, the six journeys, what was wrong, the constraints, what must survive, the vocabulary leftovers) and carries it through everything decided since: Book & Table and the six shell decisions (#363, #656), Lapis Table, and every decision D1 to D73 from the mockup round (#659), each in a line or two by area with its surfaces. It adds what the design system must provide (#364) and the build lanes in order with the server changes each needs (#366). Against this issue's acceptance criteria: - **Surface inventory** — the catalogue (#657): 1,672 rows on 107 surfaces, with the route inventory of `v4.4.0-concepts/surface-inventory.md` behind it. The brief points at both. - **The six journeys as the acceptance bar** — §2, unchanged from checkpoint A, now stated for both roles, desktop and phone, keyboard and touch. - **One vocabulary, with the mapping from every current name** — §5: the five leftovers settled (D38, D47, lane 6b's taxonomy, Shelf/Table), plus every name the redesign introduces, mapped from what it is called today. - **Existing behaviours that must be preserved** — §4, with the two that changed shape (one time rather than two, D17; the checklist as the GM's, D28) said as such. - **Written down and agreed before wireframing begins** — written; wireframing and mockups are done; **this is the point to read it and say "agreed"**, after which this issue closes and #364 can start. The catalogue's decisions table stays the authority; the brief is its readable synthesis, and a change to a decision is made there first.
claude-bot commented 2026-09-21 23:02:01 +00:00
Author
Collaborator
Copy link

The brief is complete through D85 (PR #725, merged 2026-09-21). Before asking for the owner's "agreed", two checks were run:

  1. Does every surface have a drawing, verified row by row? Yes, now. The three lanes that had never been checked (1b, 2c, 5 — 445 placements) got their coverage scripts; the audit found 26 placements counted without a still and they were drawn. All sixteen scripts pass against the live catalogue (1,706 rows on 107 surfaces).
  2. Does the brief carry lane 9? It does now: docs/design/v4.5.0-brief.md has a seventh journey (J7: a player makes a character, the GM shows a block at the table, the character levels up), four vocabulary rows (the sheet, the block, a definition, Level up), §7.11 with D74 to D85 and the seams, the sheet's components in §8, the lane 11 row's server changes, and lane 9's later phases in §10.

Waiting on: the owner's "agreed", after which this closes and #366 (the build) has its handoff.

**The brief is complete through D85 (PR #725, merged 2026-09-21).** Before asking for the owner's "agreed", two checks were run: 1. **Does every surface have a drawing, verified row by row?** Yes, now. The three lanes that had never been checked (1b, 2c, 5 — 445 placements) got their coverage scripts; the audit found 26 placements counted without a still and they were drawn. All sixteen scripts pass against the live catalogue (1,706 rows on 107 surfaces). 2. **Does the brief carry lane 9?** It does now: `docs/design/v4.5.0-brief.md` has a seventh journey (J7: a player makes a character, the GM shows a block at the table, the character levels up), four vocabulary rows (the sheet, the block, a definition, Level up), §7.11 with D74 to D85 and the seams, the sheet's components in §8, the lane 11 row's server changes, and lane 9's later phases in §10. Waiting on: the owner's "agreed", after which this closes and #366 (the build) has its handoff.
claude-bot commented 2026-09-22 01:08:34 +00:00
Author
Collaborator
Copy link

Agreed by the owner, 2026-09-22. The brief (docs/design/v4.5.0-brief.md, D1 to D85, seven journeys, the lanes in order) is the handoff to the build, together with the build plan (docs/design/v4.5.0-build-plan.md), whose five assumptions the owner confirmed at the same time. Closing; the build is tracked on #366, starting with lane 0 (#364).

**Agreed by the owner, 2026-09-22.** The brief (`docs/design/v4.5.0-brief.md`, D1 to D85, seven journeys, the lanes in order) is the handoff to the build, together with the build plan (`docs/design/v4.5.0-build-plan.md`), whose five assumptions the owner confirmed at the same time. Closing; the build is tracked on #366, starting with lane 0 (#364).
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
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#361
No description provided.