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] Full mockups with sample data — 3-5 directions for comparison #363

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

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

What

From the preferred wireframe concepts, produce 3-5 full mockups at high fidelity, populated with realistic sample data — a campaign mid-arc, several sessions in various states, a real-length transcript and summary, a populated wiki with relationships, pending lore proposals, a live recording in progress.

Sample data is not decoration here. Most of the review's findings only become visible with real content: a dropdown of sessions all reading "Untitled session", a wiki article squeezed to ~39 px of prose beside a fixed sidebar, a proposals queue that renders differently depending on whether it is empty. A mockup with three tidy placeholder rows hides exactly the problems this exercise exists to solve.

The intent is explicitly comparison and mix-and-match — these are alternatives to choose between and recombine, not sequential drafts. Each should be complete enough to judge on its own.

Acceptance criteria

  • 3-5 complete mockups covering every surface in the inventory
  • Realistic sample data throughout, including long text, many items, and empty states
  • Each mockup shown at desktop, tablet and phone widths
  • Both GM and player views represented
  • Loading, error, and in-progress states shown — not only the happy path
  • Presented for direct comparison, with elements individually adoptable
Found in the August 2026 session lifecycle review (#319). Follows the wireframe exploration. ## What From the preferred wireframe concepts, produce **3-5 full mockups** at high fidelity, **populated with realistic sample data** — a campaign mid-arc, several sessions in various states, a real-length transcript and summary, a populated wiki with relationships, pending lore proposals, a live recording in progress. Sample data is not decoration here. Most of the review's findings only become visible with real content: a dropdown of sessions all reading "Untitled session", a wiki article squeezed to ~39 px of prose beside a fixed sidebar, a proposals queue that renders differently depending on whether it is empty. A mockup with three tidy placeholder rows hides exactly the problems this exercise exists to solve. The intent is explicitly **comparison and mix-and-match** — these are alternatives to choose between and recombine, not sequential drafts. Each should be complete enough to judge on its own. ## Acceptance criteria - [ ] 3-5 complete mockups covering every surface in the inventory - [ ] Realistic sample data throughout, including long text, many items, and empty states - [ ] Each mockup shown at desktop, tablet and phone widths - [ ] Both GM and player views represented - [ ] Loading, error, and in-progress states shown — not only the happy path - [ ] Presented for direct comparison, with elements individually adoptable
claude-bot commented 2026-09-10 22:14:32 +00:00
Author
Collaborator
Copy link

Round two of the design evaluation is built and live (2026-09-10). Recording it here since this issue had no trail yet.

Why round two. Round one's eight wireframe concepts (C0 to C7) mostly went unanswered: players found them overwhelming and too abstract to react to. Three sheets came back (one player, and the GM's player and GM sheets). The owner asked for two, or three if genuinely needed, full-scale mockups with extensive sample data, hosted under questboard-dev with no login, so players and a few outside people could evaluate something concrete.

Owner decisions, which change this issue's acceptance criteria:

  • Two directions, not 3 to 5, chosen from round one's ratings: A — Book & Table (C6, the highest-rated concept and top pick on two of three sheets; GM prep borrows C3's console, and wiki plus rules lookup is reachable at the table) and B — Session First (C2, second overall and the player sheet's top pick; its Review phase decluttered, keeping verified events beside the summary).
  • Invented sample data, not the real campaign, because people outside the campaign will see it. "The Amberwake Accord": fourteen sessions including two cancellations, a 63-entry wiki grown unevenly, an absent player, an undecided RSVP.

What was built. Both mockups share one design system and one data file, so they can only differ in structure, never in polish. Five screens each in phone and desktop frames: home, the session that matters (this week / Plan), the table during a session (GM desktop, player phone), after the session with the event log from #568, and GM prep. Hosted on the feedback site as audience round2 (#590) with a deliberately short form; the landing page is https://questboard-dev.rhoving.com/feedback/mockups (the invitation link carries the key that lets answers save).

Bug on first real use, fixed. The design links were root-relative, so behind the /feedback/ prefix they led to the Quest Board login page, and a trailing slash did the same through Starlette's slash redirect. Fixed and deployed, with a test that no page carries a root-relative link: see the PR opened alongside this comment.

Against the acceptance criteria:

  • Done: realistic sample data with long text and many items; GM and player views; an in-progress state (a live session at the table); presented for direct comparison.
  • Not done: 3 to 5 mockups (two, by the owner's decision); tablet width (phone and desktop only); loading and error states; every surface in the inventory (five core screens each).

Next: collect the round-two responses, bring them back, and settle the final design (#364). Leaving this open until then.

**Round two of the design evaluation is built and live (2026-09-10).** Recording it here since this issue had no trail yet. **Why round two.** Round one's eight wireframe concepts (C0 to C7) mostly went unanswered: players found them overwhelming and too abstract to react to. Three sheets came back (one player, and the GM's player and GM sheets). The owner asked for two, or three if genuinely needed, full-scale mockups with extensive sample data, hosted under questboard-dev with no login, so players and a few outside people could evaluate something concrete. **Owner decisions, which change this issue's acceptance criteria:** - **Two directions, not 3 to 5**, chosen from round one's ratings: **A — Book & Table** (C6, the highest-rated concept and top pick on two of three sheets; GM prep borrows C3's console, and wiki plus rules lookup is reachable at the table) and **B — Session First** (C2, second overall and the player sheet's top pick; its Review phase decluttered, keeping verified events beside the summary). - **Invented sample data, not the real campaign**, because people outside the campaign will see it. "The Amberwake Accord": fourteen sessions including two cancellations, a 63-entry wiki grown unevenly, an absent player, an undecided RSVP. **What was built.** Both mockups share one design system and one data file, so they can only differ in structure, never in polish. Five screens each in phone and desktop frames: home, the session that matters (this week / Plan), the table during a session (GM desktop, player phone), after the session with the event log from #568, and GM prep. Hosted on the feedback site as audience `round2` (#590) with a deliberately short form; the landing page is `https://questboard-dev.rhoving.com/feedback/mockups` (the invitation link carries the key that lets answers save). **Bug on first real use, fixed.** The design links were root-relative, so behind the `/feedback/` prefix they led to the Quest Board login page, and a trailing slash did the same through Starlette's slash redirect. Fixed and deployed, with a test that no page carries a root-relative link: see the PR opened alongside this comment. **Against the acceptance criteria:** - Done: realistic sample data with long text and many items; GM and player views; an in-progress state (a live session at the table); presented for direct comparison. - Not done: 3 to 5 mockups (two, by the owner's decision); tablet width (phone and desktop only); loading and error states; every surface in the inventory (five core screens each). **Next:** collect the round-two responses, bring them back, and settle the final design (#364). Leaving this open until then.
claude-bot commented 2026-09-11 02:21:44 +00:00
Author
Collaborator
Copy link

Round two now includes the wiki (2026-09-11). Before sending round two out, the owner wanted the wiki designed and in front of players too. The design was worked out with them and recorded in #593, and both mockups now carry it (PR #594, live on dev).

  • Six new screens in each design (6–11): front page and search, an NPC article with its stat block, editing, the map, the party, and a quest. They're built from shared components, so A and B differ only in how the wiki fits into each design:
    • A: a group of chapters in the book's Contents.
    • B: a World destination beside the session strip.
  • The form gained one wiki rating per design and "What would you want from the wiki that isn't there?".
  • Invented data, still. The Amberwake campaign grew a wiki: maps in two atlases joined by a portal, a party with members who came and went, quests, handouts given to one player, and an unidentified ring.
  • Checked: crawls of every player-view frame found none of the 89 GM-only strings. The crawls also turned up two real visibility gaps in the shared helpers, which were fixed before release; #593 has the details, because they matter for the real build.

Same link as before. Nothing has changed for anyone who already has it, and nobody had answered round two yet. Still open until the round-two responses are read.

**Round two now includes the wiki (2026-09-11).** Before sending round two out, the owner wanted the wiki designed and in front of players too. The design was worked out with them and recorded in #593, and both mockups now carry it (PR #594, live on dev). - **Six new screens in each design** (6–11): front page and search, an NPC article with its stat block, editing, the map, the party, and a quest. They're built from shared components, so A and B differ only in how the wiki fits into each design: - **A:** a group of chapters in the book's Contents. - **B:** a World destination beside the session strip. - **The form** gained one wiki rating per design and "What would you want from the wiki that isn't there?". - **Invented data, still.** The Amberwake campaign grew a wiki: maps in two atlases joined by a portal, a party with members who came and went, quests, handouts given to one player, and an unidentified ring. - **Checked:** crawls of every player-view frame found none of the 89 GM-only strings. The crawls also turned up two real visibility gaps in the shared helpers, which were fixed before release; #593 has the details, because they matter for the real build. Same link as before. Nothing has changed for anyone who already has it, and nobody had answered round two yet. Still open until the round-two responses are read.
claude-bot commented 2026-09-15 16:22:02 +00:00
Author
Collaborator
Copy link

Round-two responses so far, read (2026-09-15). Three responses: the owner and two players. One player sent their reaction to the owner as a direct message rather than using the form. It has been added to the feedback store by hand as round2-aidanmessage0915.json: their words sit in the matching fields, with no ratings, and the name on the card says it came by message. The original text is kept in originalMessage.

Headline: A (Book & Table) on every response, and B scores lower everywhere.

A · Book & Table B · Session First
Would rather use 3 of 3 (one "probably") 0
Could find what I needed (2 rated) 5.0 3.0
Would use at the table (2 rated) 5.0 2.5
Wiki easy to get around (2 rated) 5.0 3.5

Worth borrowing from B: the "Are you in?" block (B's roster-with-count version), the wiki's Map / Party / Quests tabs, and easier access to the generators. A player called B "lots of noise", and the same player said of A: "no extra info to confuse me".

Other themes:

  • Look: more colour and custom icons. Both mockups share one design system, so this goes to #364, not to the A/B choice.
  • GM at the table: more prep and generator tools on the running-session page. This repeats round one: beats and arcs, random names, rules and bestiary lookup.
  • Wiki: bring the original categories over; find a place for rulebooks, bestiaries and imported content; one player asked for a "message the DM / ask a question" section, possibly as threaded posts.
  • Pronoun fields for players, PCs and NPCs (the owner, marked as needed).

Caveat: only two sets of ratings, one of them the owner's. No outside-link responses yet, and no GM other than the owner. Still open until the owner settles the direction.

**Round-two responses so far, read (2026-09-15).** Three responses: the owner and two players. One player sent their reaction to the owner as a direct message rather than using the form. It has been added to the feedback store by hand as `round2-aidanmessage0915.json`: their words sit in the matching fields, with no ratings, and the name on the card says it came by message. The original text is kept in `originalMessage`. **Headline: A (Book & Table) on every response, and B scores lower everywhere.** | | A · Book & Table | B · Session First | |---|---|---| | Would rather use | 3 of 3 (one "probably") | 0 | | Could find what I needed (2 rated) | 5.0 | 3.0 | | Would use at the table (2 rated) | 5.0 | 2.5 | | Wiki easy to get around (2 rated) | 5.0 | 3.5 | **Worth borrowing from B:** the "Are you in?" block (B's roster-with-count version), the wiki's Map / Party / Quests tabs, and easier access to the generators. A player called B "lots of noise", and the same player said of A: "no extra info to confuse me". **Other themes:** - **Look:** more colour and custom icons. Both mockups share one design system, so this goes to #364, not to the A/B choice. - **GM at the table:** more prep and generator tools on the running-session page. This repeats round one: beats and arcs, random names, rules and bestiary lookup. - **Wiki:** bring the original categories over; find a place for rulebooks, bestiaries and imported content; one player asked for a "message the DM / ask a question" section, possibly as threaded posts. - **Pronoun fields** for players, PCs and NPCs (the owner, marked as needed). **Caveat:** only two sets of ratings, one of them the owner's. No outside-link responses yet, and no GM other than the owner. Still open until the owner settles the direction.
claude-bot commented 2026-09-15 16:45:59 +00:00
Author
Collaborator
Copy link

Direction settled (2026-09-15): A (Book & Table) is the base, with elements of B pulled in. This is the owner's decision after reading the round-two responses.

Taken from B, as named in the feedback:

  • the "Are you in?" block in B's version: a roster with a count of who's in
  • the wiki's Map / Party / Quests tabs, alongside A's way of browsing (#593)
  • quicker access to the generators, before and during a session

Where the rest of the feedback goes:

  • Colour and custom icons: #364. Both mockups share one design system, so this was never an A-vs-B question.
  • More GM tools on the running-session page: #365.
  • Wiki categories and rules content: already in #593, which keeps all 13 types and adds a Rules section. When the wiki is built, check that A's grouped Contents still reaches every type.
  • Pronouns: #653. Most of the data already exists; the gaps are a field for players, showing pronouns consistently, and passing them to the prompts.
  • Player questions to the GM: #654. It is kept separate from #121's anonymous safety flag.

This still needs writing into the brief (#361) before #364 starts.

Closing: the comparison has done its job. Late responses still reach the feedback store and can be read in the readout.

**Direction settled (2026-09-15): A (Book & Table) is the base, with elements of B pulled in.** This is the owner's decision after reading the round-two responses. **Taken from B,** as named in the feedback: - the "Are you in?" block in B's version: a roster with a count of who's in - the wiki's Map / Party / Quests tabs, alongside A's way of browsing (#593) - quicker access to the generators, before and during a session **Where the rest of the feedback goes:** - **Colour and custom icons:** #364. Both mockups share one design system, so this was never an A-vs-B question. - **More GM tools on the running-session page:** #365. - **Wiki categories and rules content:** already in #593, which keeps all 13 types and adds a Rules section. When the wiki is built, check that A's grouped Contents still reaches every type. - **Pronouns:** #653. Most of the data already exists; the gaps are a field for players, showing pronouns consistently, and passing them to the prompts. - **Player questions to the GM:** #654. It is kept separate from #121's anonymous safety flag. This still needs writing into the brief (#361) before #364 starts. Closing: the comparison has done its job. Late responses still reach the feedback store and can be read in the readout.
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#363
No description provided.