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

Wiki infobox: suggested facts by page type, a picture caption, a map as the picture, and a title bar #1279

New issue
Closed
opened 2026-10-29 17:18:51 +00:00 by claude-bot · 6 comments
claude-bot commented 2026-10-29 17:18:51 +00:00
Collaborator
Copy link

The owner, 2026-10-29, comparing the page margin with Wikipedia's infobox (Pathfinder RPG as the example). The margin already has a picture and free label/value Facts (sidebar_fields); the owner hadn't found that facts could be added, and wants the editor to prompt for the important details instead of relying on memory.

Scope (the owner: "those four options are probably a good start")

  1. Suggested facts by page type. The editor's Facts panel starts with that type's fields, empty. A blank field is never shown to readers. Fields can still be removed, renamed or added. Changing a page's type offers the new type's fields without losing what's already filled in.
  2. A caption under the picture.
  3. A map as the picture: choose one of the campaign's maps, shown as its thumbnail and linking to the map, with the reader's audience checked as ![[Map: X]] already does.
  4. A title bar with the page's name at the top of the box.

Proposed fields by type (draft for the owner to review; a value can link to a page with [[…]]). Things the page already holds elsewhere are not repeated: pronouns, "Also called", stat blocks and sheets, an artifact's holder, timeline events, and "On the map".

Type Fields
Player Character Player · Ancestry · Class · Level · Background · Home · Allegiances
NPC Role · Ancestry · Home · Allegiances · Status (alive / dead / missing / unknown) · First met
Settlement Region · Size · Population · Ruler · Allegiance · Notable places · Known for
Country Capital · Ruler · Government · Population · Languages · Religion · Currency · Allies · Rivals
Geography Kind (forest, mountain, sea…) · Region · Climate · Dangers · Inhabitants · Notable places
Organization Leader · Headquarters · Founded · Goals · Allies · Rivals · Symbol
Deity Domains · Alignment · Symbol · Worshippers · Holy days · Allies · Rivals
Business Owner · Location · Trade · Prices · Hours · Staff
Historical Event Date · Place · Involved · Outcome · Aftermath
Artifact Kind · Rarity · Attunement · Powers · Made by · Origin
Creature Type · Size · Habitat · Diet · Danger · Behaviour
Concept Kind (magic, law, custom…) · Known to · Origin
Document Author · Written · Language · Where kept · Kind

Open questions for the owner

  • Should some fields be per game system (e.g. Alignment only where the system has it)? The campaign's game system is known.
  • A GM-only fact, e.g. an NPC's true allegiance? Today facts are visible to whoever can read the page; this may want the wiki's GM-block audience.
  • Should "First met" and "Status" fill themselves in from sessions, or stay hand-written?

Release: new functionality → 4.7.0 (the X.Y.0 / X.Y.Z rule).

The owner, 2026-10-29, comparing the page margin with Wikipedia's infobox (Pathfinder RPG as the example). The margin already has a picture and free label/value **Facts** (`sidebar_fields`); the owner hadn't found that facts could be added, and wants the editor to **prompt for the important details** instead of relying on memory. **Scope (the owner: "those four options are probably a good start")** 1. **Suggested facts by page type.** The editor's Facts panel starts with that type's fields, empty. A blank field is never shown to readers. Fields can still be removed, renamed or added. Changing a page's type offers the new type's fields without losing what's already filled in. 2. **A caption** under the picture. 3. **A map as the picture**: choose one of the campaign's maps, shown as its thumbnail and linking to the map, with the reader's audience checked as `![[Map: X]]` already does. 4. **A title bar** with the page's name at the top of the box. **Proposed fields by type** (draft for the owner to review; a value can link to a page with `[[…]]`). Things the page already holds elsewhere are **not** repeated: pronouns, "Also called", stat blocks and sheets, an artifact's holder, timeline events, and "On the map". | Type | Fields | |---|---| | Player Character | Player · Ancestry · Class · Level · Background · Home · Allegiances | | NPC | Role · Ancestry · Home · Allegiances · Status (alive / dead / missing / unknown) · First met | | Settlement | Region · Size · Population · Ruler · Allegiance · Notable places · Known for | | Country | Capital · Ruler · Government · Population · Languages · Religion · Currency · Allies · Rivals | | Geography | Kind (forest, mountain, sea…) · Region · Climate · Dangers · Inhabitants · Notable places | | Organization | Leader · Headquarters · Founded · Goals · Allies · Rivals · Symbol | | Deity | Domains · Alignment · Symbol · Worshippers · Holy days · Allies · Rivals | | Business | Owner · Location · Trade · Prices · Hours · Staff | | Historical Event | Date · Place · Involved · Outcome · Aftermath | | Artifact | Kind · Rarity · Attunement · Powers · Made by · Origin | | Creature | Type · Size · Habitat · Diet · Danger · Behaviour | | Concept | Kind (magic, law, custom…) · Known to · Origin | | Document | Author · Written · Language · Where kept · Kind | **Open questions for the owner** - Should some fields be per game system (e.g. Alignment only where the system has it)? The campaign's game system is known. - A GM-only fact, e.g. an NPC's true allegiance? Today facts are visible to whoever can read the page; this may want the wiki's GM-block audience. - Should "First met" and "Status" fill themselves in from sessions, or stay hand-written? **Release:** new functionality → 4.7.0 (the X.Y.0 / X.Y.Z rule).
claude-bot commented 2026-10-29 17:27:25 +00:00
Author
Collaborator
Copy link

The owner's decisions (2026-10-29):

  1. Pronouns on PC, NPC and Deity pages. NPC and PC already have pronouns (HAS_PRONOUNS in editorText.js), shown beside the title; Deity is new. The infobox shows them too. The player's pronouns follow their name in a PC's "Player" fact, when set (users.pronouns).
  2. Fields by game system: the suggested facts depend on the campaign's system, using what that system uses (e.g. Alignment, or Class/Level as the system names them), with a system-neutral set for "generic".
  3. Filled from a content pack: a page made from or "based on" a rules entry (source_reference_entry_id) fills the matching facts from that entry.
  4. Fact visibility: GMs set who sees each fact, like the wiki's restricted blocks (GMs only, or chosen players). Already built: RowsEditor gives every fact row its own "Who sees it", and wiki_audience.visible_items filters sidebar_fields per reader. The owner hadn't found it, so this item is about making it discoverable in the new infobox editor, not building it.
  5. Suggested updates fill facts. Start with "First met" and "Status", then extend. Proposed staging, pending the owner's answer:
    • Stage 1, no AI: First met / Last seen from lore_session_appearances; Player (+ pronouns) from the campaign member; class, level and ancestry from a character sheet; content-pack fields; a place's Region from the map it sits on.
    • Stage 2, the self-hosted model, as suggestions a GM approves: one narrow, schema-constrained question per page that appeared in a session ("did this one's status, leader, ruler, owner or allegiance change?"), each answer carrying a quote from the transcript, which is checked against it the way summary beats are. GM-only until approved, through the existing draft review.
    • Not attempted: open-ended inference (a settlement's population, an implied motive) and synthesis across many sessions. Too unreliable on the local model.
**The owner's decisions (2026-10-29):** 1. **Pronouns** on PC, NPC and **Deity** pages. NPC and PC already have `pronouns` (`HAS_PRONOUNS` in `editorText.js`), shown beside the title; Deity is new. The infobox shows them too. **The player's pronouns** follow their name in a PC's "Player" fact, when set (`users.pronouns`). 2. **Fields by game system:** the suggested facts depend on the campaign's system, using what that system uses (e.g. Alignment, or Class/Level as the system names them), with a system-neutral set for "generic". 3. **Filled from a content pack:** a page made from or "based on" a rules entry (`source_reference_entry_id`) fills the matching facts from that entry. 4. **Fact visibility:** GMs set who sees each fact, like the wiki's restricted blocks (GMs only, or chosen players). **Already built:** `RowsEditor` gives every fact row its own "Who sees it", and `wiki_audience.visible_items` filters `sidebar_fields` per reader. The owner hadn't found it, so this item is about making it discoverable in the new infobox editor, not building it. 5. **Suggested updates fill facts.** Start with "First met" and "Status", then extend. Proposed staging, pending the owner's answer: - **Stage 1, no AI:** First met / Last seen from `lore_session_appearances`; Player (+ pronouns) from the campaign member; class, level and ancestry from a character sheet; content-pack fields; a place's Region from the map it sits on. - **Stage 2, the self-hosted model, as suggestions a GM approves:** one narrow, schema-constrained question per page that appeared in a session ("did this one's status, leader, ruler, owner or allegiance change?"), each answer carrying a quote from the transcript, which is checked against it the way summary beats are. GM-only until approved, through the existing draft review. - **Not attempted:** open-ended inference (a settlement's population, an implied motive) and synthesis across many sessions. Too unreliable on the local model.
claude-bot commented 2026-10-29 17:32:26 +00:00
Author
Collaborator
Copy link

The owner agreed the staging (2026-10-29). Stage 2, facts suggested by the local model, is split out as #1280. This issue keeps stage 1 (no AI) together with the infobox itself.

The owner agreed the staging (2026-10-29). Stage 2, facts suggested by the local model, is split out as #1280. This issue keeps stage 1 (no AI) together with the infobox itself.
claude-bot commented 2026-11-03 00:17:56 +00:00
Author
Collaborator
Copy link

Picking this up (stage 1, no AI). First, a drawing on the prototype lane: the reader's infobox (title bar, picture or map with caption, the facts that are filled, with pronouns) and the editor's Facts panel (the type's suggested fields, empty, plus "Who sees it" on each). The per-system field lists go to the owner as questions before anything is built.

Picking this up (stage 1, no AI). First, a drawing on the prototype lane: the reader's infobox (title bar, picture or map with caption, the facts that are filled, with pronouns) and the editor's Facts panel (the type's suggested fields, empty, plus "Who sees it" on each). The per-system field lists go to the owner as questions before anything is built.
claude-bot commented 2026-11-03 00:38:13 +00:00
Author
Collaborator
Copy link

The owner's answers (2026-11-03), recorded as D319–D322 (commit 4e7e9127 on design/1279-infobox; the drawing is lane 6i):

  • Q210 → D319: the suggested-fact lists are right as drawn, per type and per system (Pathfinder 2e, D&D 5e, Generic).
  • Q211 → D320: facts Quest Board already knows stay live. Readers see the known value while the fact is empty, and typing a value overrides it.
  • Q212 → D321: a map can be the picture on any page type.
  • Q213 → D322: readers see only the value, not its source. Pronouns move into the box and no longer sit under the title.

Building now.

**The owner's answers (2026-11-03), recorded as D319–D322** (commit 4e7e9127 on `design/1279-infobox`; the drawing is lane 6i): - **Q210 → D319:** the suggested-fact lists are right as drawn, per type and per system (Pathfinder 2e, D&D 5e, Generic). - **Q211 → D320:** facts Quest Board already knows stay live. Readers see the known value while the fact is empty, and typing a value overrides it. - **Q212 → D321:** a map can be the picture on any page type. - **Q213 → D322:** readers see only the value, not its source. Pronouns move into the box and no longer sit under the title. Building now.
claude-bot commented 2026-11-03 04:55:23 +00:00
Author
Collaborator
Copy link

Prod check and fix (owner's ask, 2026-11-03):

  • One live prod campaign, World Quest (created 14 Mar, before the game system registry, #133), had "Pathfinder 2e" as free text but no game_system_id. It therefore read as Generic for rules browsing, sheets and these suggested facts.
  • At the owner's explicit request I linked it to pf2e with a one-row update, guarded on its id and on game_system_id still being null. The before state was game_system_id = NULL; to undo, set it back to null.
  • All 3 live campaigns now read as pf2e.
  • The registry migration never linked existing campaigns by name. No migration was added, because nobody else runs Quest Board today.
**Prod check and fix (owner's ask, 2026-11-03):** - One live prod campaign, World Quest (created 14 Mar, before the game system registry, #133), had "Pathfinder 2e" as free text but no `game_system_id`. It therefore read as Generic for rules browsing, sheets and these suggested facts. - At the owner's explicit request I linked it to pf2e with a one-row update, guarded on its id and on `game_system_id` still being null. The before state was `game_system_id = NULL`; to undo, set it back to null. - All 3 live campaigns now read as `pf2e`. - The registry migration never linked existing campaigns by name. No migration was added, because nobody else runs Quest Board today.
claude-bot commented 2026-11-03 06:46:11 +00:00
Author
Collaborator
Copy link

Done: stage 1 merged in #1324 (D319–D322, lane 6i).

  • Reader: one box with a title bar, the type, the picture or a map with a caption, pronouns as the first row (PC, NPC, Deity), and then only the filled facts.
  • Known facts: First met and Last seen, Player with pronouns, sheet values, a place's Region, and rules-entry fields. They are computed per reader and never stored. A written value, even a GMs-only one, always suppresses its known value.
  • Editor: each page type starts with its suggested facts by system. A known value shows greyed with its source. Removing a suggestion dismisses it, and changing the type adds facts without dropping any. The Picture panel offers "A picture | A map" with a caption.
  • Server: migration e1279a0b1c2d adds image_caption, image_map_id and facts_dismissed. The suggested lists live in app/services/suggested_facts.json, beside a new GET …/wiki/suggested-facts. Export, import and setup copy all carry the new fields.
  • Checks:
    • The render check was clean: 36 shots, axe clean, title bar contrast 7.8:1 and 8.3:1.
    • The owner approved the wording (part s).
    • CI passed. It first caught two older migration round trips and a title-reader guard, all fixed in tests only.
  • Prod: World Quest is now linked to Pathfinder 2e (see above).

Stage 2, facts suggested by the local model, is #1280.

**Done:** stage 1 merged in #1324 (D319–D322, lane 6i). - **Reader:** one box with a title bar, the type, the picture or a map with a caption, pronouns as the first row (PC, NPC, Deity), and then only the filled facts. - **Known facts:** First met and Last seen, Player with pronouns, sheet values, a place's Region, and rules-entry fields. They are computed per reader and never stored. A written value, even a GMs-only one, always suppresses its known value. - **Editor:** each page type starts with its suggested facts by system. A known value shows greyed with its source. Removing a suggestion dismisses it, and changing the type adds facts without dropping any. The Picture panel offers "A picture | A map" with a caption. - **Server:** migration `e1279a0b1c2d` adds `image_caption`, `image_map_id` and `facts_dismissed`. The suggested lists live in `app/services/suggested_facts.json`, beside a new `GET …/wiki/suggested-facts`. Export, import and setup copy all carry the new fields. - **Checks:** - The render check was clean: 36 shots, axe clean, title bar contrast 7.8:1 and 8.3:1. - The owner approved the wording (part s). - CI passed. It first caught two older migration round trips and a title-reader guard, all fixed in tests only. - **Prod:** World Quest is now linked to Pathfinder 2e (see above). Stage 2, facts suggested by the local model, is #1280.
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#1279
No description provided.