rbrooks/Quest-Board

Watch

Fork

You've already forked Quest-Board

Code Issues 58 Pull requests 7 Projects Releases 76 Packages Wiki Activity Actions

[Backend] Support multiple characters per player #330

New issue

Closed

opened 2026-08-25 20:38:49 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-08-25 20:38:49 +00:00

Collaborator

Copy link

Severity: MEDIUM. Found in the August 2026 session lifecycle review (#319).

The defect

CampaignMember.character_name is a single column, so a player running two characters — a main and a sidekick, a party of two, a character who dies and is replaced mid-campaign — cannot be represented. Every line that player speaks is attributed to whichever single character is recorded, and the summary confidently credits the wrong one.

This also interacts badly with attribution: the character map is keyed by display name, so there is no way to express "this line was Kira, that line was the familiar".

Proposed fix

Move to a per-member list of characters with an optional active/primary flag, and allow a per-session override so a character swap partway through a campaign does not rewrite history. Keep the existing single-name behaviour as the degenerate case so nothing breaks on migration.

Attribution stays deterministic: with more than one character on a member, the resolver labels lines with the player's display name plus the active character rather than guessing per line, and the legend records all of that member's characters so the beat validator can accept any of them as a valid actor for that speaker.

Acceptance criteria

A member can have multiple characters, with one marked active
A session can override which character was active
Migration preserves every existing character_name with no user action
The speaker legend lists all characters belonging to a member
The beat validator accepts any of a member's characters as a valid actor for that speaker's lines
UI allows a GM, and a player for their own membership, to manage the list

**Severity: MEDIUM.** Found in the August 2026 session lifecycle review (#319). ## The defect `CampaignMember.character_name` is a single column, so a player running two characters — a main and a sidekick, a party of two, a character who dies and is replaced mid-campaign — cannot be represented. Every line that player speaks is attributed to whichever single character is recorded, and the summary confidently credits the wrong one. This also interacts badly with attribution: the character map is keyed by display name, so there is no way to express "this line was Kira, that line was the familiar". ## Proposed fix Move to a per-member list of characters with an optional active/primary flag, and allow a per-session override so a character swap partway through a campaign does not rewrite history. Keep the existing single-name behaviour as the degenerate case so nothing breaks on migration. Attribution stays deterministic: with more than one character on a member, the resolver labels lines with the player's display name plus the active character rather than guessing per line, and the legend records all of that member's characters so the beat validator can accept any of them as a valid actor for that speaker. ## Acceptance criteria - [ ] A member can have multiple characters, with one marked active - [ ] A session can override which character was active - [ ] Migration preserves every existing `character_name` with no user action - [ ] The speaker legend lists all characters belonging to a member - [ ] The beat validator accepts any of a member's characters as a valid actor for that speaker's lines - [ ] UI allows a GM, and a player for their own membership, to manage the list

claude-bot added this to the v4.0.0 - Session Pipeline Accuracy milestone

2026-08-25 20:38:49 +00:00

claude-bot added the

enhancement

backend

frontend

labels

2026-08-25 20:38:49 +00:00

rbrooks referenced this issue from a commit

2026-08-26 16:23:01 +00:00

feat(backend): let a player run more than one character (#330)

rbrooks referenced this issue from a commit

2026-08-26 16:45:23 +00:00

feat(frontend): manage a player's characters, and keep their sheet theirs (#330)

claude-bot commented

2026-08-26 16:45:49 +00:00

Author

Collaborator

Copy link

Done on feat/v4-deterministic-attribution in two commits: c4ffad2 (backend) and b551a08 (UI).

Acceptance

A member can have multiple characters, with one marked active
A session can override which character was active
Migration preserves every existing character_name with no user action
The speaker legend lists all characters belonging to a member
The beat validator accepts any of a member's characters as a valid actor for that speaker's lines
UI allows a GM, and a player for their own membership, to manage the list

1,130 backend tests passing before → 1,165; frontend 440 (CampaignDetail 30 → 39).

The one design call worth recording

The issue says the resolver should label lines with "the player's display name plus the active character". I built that, but the reasoning is worth writing down because it looks like a downgrade and isn't.

With one character nothing changes — the label is still the character name, and test_speaker_service.py's existing cases were untouched. With two or more, the label becomes ash (Kira). Labelling every line Kira would assert something no evidence supports: one Discord account carries every character its owner plays, and audio cannot say which one spoke a line, so the familiar's lines would be filed under the main character. The track proves who the player is, so the player leads.

That only works because of the last two acceptance criteria together. The legend names every character, and the validator accepts any of them — so a beat correctly attributed to Whiskers still passes even though the transcript label says Kira. Without the validator half this feature would be actively worse than the bug: correct attributions would be rejected as invented names. The alias map is scoped to characters of speakers who actually spoke a cited line, so it doesn't become a hole any invented name fits through — test_a_character_belonging_to_nobody_is_still_rejected pins that.

Two things the issue didn't anticipate

Member erasure was scrubbing only the current character. _labels_for_owner added member.character_name; a player who swapped characters mid-campaign appears in older transcripts under the old name, so erasing only the active one would leave those lines attributed to someone who asked to be removed. It now uses character_names. Not in the acceptance criteria, but shipping multi-character without it would have created a data-protection bug that did not previously exist.

A permission boundary nearly went missing. The pre-#330 member PATCH split character fields two ways: a GM acting on someone else could set name/pronouns/wiki-link but not sheet URL or sheet notes; a player could set their sheet fields but not link an arbitrary wiki page. The new character endpoints carried across only the lore-link half, so a GM could edit any player's sheet notes. Both directions now go through one router helper, with tests for each direction and for the create path, which had the same hole. Flagging it here because it is the classic shape of a refactor regression: the surviving half makes the code look like it enforces a policy.

Migration is expand-only

campaign_characters (composite FK to campaign_members, partial unique index for one-active-per-member) and session_character_overrides. The five campaign_members.character_* columns are backfilled and then left in place, unmapped by the ORM — a downgrade is two DROP TABLEs and no data is ever at risk, which is what I want on a database holding recordings that cannot be re-made. It also sidesteps the one row shape a contract would lose: a member who set a sheet URL but never named their character, who would otherwise need backfilling under an invented name that then shows up as a transcript speaker label. Dropping the columns is a later contract migration.

Verified against a real Postgres, because the test suite builds schema with create_all and never runs Alembic: full chain applies clean, backfill trims whitespace and copies all five fields and skips a null-character GM, the partial index rejects a second active and permits a second inactive, deleting a membership takes its characters, and downgrade + re-upgrade leaves the source columns intact.

The five character_* names survive as read-only properties over the active character, so the ~24 read sites were untouched and cannot drift from the table. characters is lazy="selectin" — a lazy load under asyncio raises rather than returning a wrong answer, and auditing two dozen query sites for a selectinload they must never forget is a worse bet than one extra SELECT per member query.

Notes for later

Export is schema 9: a characters list per member, with the flat character_name keys still populated from the active character so a v9 export restores into an older Quest Board. Imports of 2–8 fall back to the flat keys unchanged.
PUT /sessions/{id}/character-overrides/{user_id} lives on the sessions router. It first landed under /api/campaigns/sessions/... to dodge the route-ordering rule; moved before anything depends on it.
UnlinkedMember still carries one inline character. An export describes one per member, and the claim path converts it — with link_lore=False, because claiming a stub restores recorded state rather than creating something new, and re-deriving the link silently promoted a recorded secondary owner to primary.
No per-session override UI yet. The endpoint is GM-only and tested, but nothing in the frontend calls it, so today a swap has to be pinned via the API. Worth its own issue — say the word and I'll open one.

Done on `feat/v4-deterministic-attribution` in two commits: `c4ffad2` (backend) and `b551a08` (UI). ## Acceptance - [x] A member can have multiple characters, with one marked active - [x] A session can override which character was active - [x] Migration preserves every existing `character_name` with no user action - [x] The speaker legend lists all characters belonging to a member - [x] The beat validator accepts any of a member's characters as a valid actor for that speaker's lines - [x] UI allows a GM, and a player for their own membership, to manage the list 1,130 backend tests passing before → **1,165**; frontend **440** (CampaignDetail 30 → 39). ## The one design call worth recording The issue says the resolver should label lines with "the player's display name plus the active character". I built that, but the reasoning is worth writing down because it looks like a downgrade and isn't. With **one** character nothing changes — the label is still the character name, and `test_speaker_service.py`'s existing cases were untouched. With **two or more**, the label becomes `ash (Kira)`. Labelling every line `Kira` would assert something no evidence supports: one Discord account carries every character its owner plays, and audio cannot say which one spoke a line, so the familiar's lines would be filed under the main character. The track proves who the *player* is, so the player leads. That only works because of the last two acceptance criteria together. The legend names every character, and the validator accepts any of them — so a beat correctly attributed to Whiskers still passes even though the transcript label says Kira. Without the validator half this feature would be actively worse than the bug: correct attributions would be rejected as invented names. The alias map is scoped to characters of speakers who actually spoke a cited line, so it doesn't become a hole any invented name fits through — `test_a_character_belonging_to_nobody_is_still_rejected` pins that. ## Two things the issue didn't anticipate **Member erasure was scrubbing only the current character.** `_labels_for_owner` added `member.character_name`; a player who swapped characters mid-campaign appears in older transcripts under the old name, so erasing only the active one would leave those lines attributed to someone who asked to be removed. It now uses `character_names`. Not in the acceptance criteria, but shipping multi-character without it would have created a data-protection bug that did not previously exist. **A permission boundary nearly went missing.** The pre-#330 member PATCH split character fields two ways: a GM acting on someone else could set name/pronouns/wiki-link but *not* sheet URL or sheet notes; a player could set their sheet fields but not link an arbitrary wiki page. The new character endpoints carried across only the lore-link half, so a GM could edit any player's sheet notes. Both directions now go through one router helper, with tests for each direction and for the create path, which had the same hole. Flagging it here because it is the classic shape of a refactor regression: the surviving half makes the code *look* like it enforces a policy. ## Migration is expand-only `campaign_characters` (composite FK to `campaign_members`, partial unique index for one-active-per-member) and `session_character_overrides`. The five `campaign_members.character_*` columns are backfilled and then **left in place, unmapped by the ORM** — a downgrade is two `DROP TABLE`s and no data is ever at risk, which is what I want on a database holding recordings that cannot be re-made. It also sidesteps the one row shape a contract would lose: a member who set a sheet URL but never named their character, who would otherwise need backfilling under an invented name that then shows up as a transcript speaker label. Dropping the columns is a later contract migration. Verified against a real Postgres, because the test suite builds schema with `create_all` and never runs Alembic: full chain applies clean, backfill trims whitespace and copies all five fields and skips a null-character GM, the partial index rejects a second active and permits a second inactive, deleting a membership takes its characters, and downgrade + re-upgrade leaves the source columns intact. The five `character_*` names survive as read-only properties over the active character, so the ~24 read sites were untouched and cannot drift from the table. `characters` is `lazy="selectin"` — a lazy load under asyncio raises rather than returning a wrong answer, and auditing two dozen query sites for a `selectinload` they must never forget is a worse bet than one extra SELECT per member query. ## Notes for later - Export is schema **9**: a `characters` list per member, with the flat `character_name` keys still populated from the active character so a v9 export restores into an older Quest Board. Imports of 2–8 fall back to the flat keys unchanged. - `PUT /sessions/{id}/character-overrides/{user_id}` lives on the sessions router. It first landed under `/api/campaigns/sessions/...` to dodge the route-ordering rule; moved before anything depends on it. - `UnlinkedMember` still carries one inline character. An export describes one per member, and the claim path converts it — with `link_lore=False`, because claiming a stub restores recorded state rather than creating something new, and re-deriving the link silently promoted a recorded `secondary` owner to `primary`. - **No per-session override UI yet.** The endpoint is GM-only and tested, but nothing in the frontend calls it, so today a swap has to be pinned via the API. Worth its own issue — say the word and I'll open one.

claude-bot closed this issue

2026-08-26 16:45:52 +00:00

claude-bot referenced this issue

2026-08-26 16:59:25 +00:00

[Frontend] Let a GM pin which character a player was running for a past session #422

rbrooks referenced this issue from a commit

2026-08-28 00:45:01 +00:00

feat(backend): persist the events a summary was built from (#332, #333, #329)

claude-bot referenced this issue

2026-08-28 19:15:21 +00:00

[Backend] Resolve every speaker label to a character in code, and delete the prompt-time rename #329

rbrooks referenced this issue from a commit

2026-08-28 23:36:51 +00:00

fix(backend): repair two CI gates this branch never ran against

claude-bot referenced this issue

2026-08-29 18:19:16 +00:00

[Review] Standards and consistency pass across API, errors, migrations and conventions #445

rbrooks referenced this issue from a commit

2026-09-06 00:55:15 +00:00

test(webapp): lock in that players can set their own character name (#383)

claude-bot referenced this issue

2026-09-06 00:55:26 +00:00

fix(webapp): three small product-surface fixes (phase 1 of v4.3.0) #515

claude-bot referenced this issue

2026-09-06 01:13:09 +00:00

[Frontend] Let players set their own character name #383

claude-bot referenced this issue

2026-09-06 02:01:27 +00:00

chore(release): v4.2.3 #518

claude-bot referenced this issue

2026-09-06 02:23:52 +00:00

v4.3.0 build order: Product Surface in eight phases #514

claude-bot referenced this issue

2026-09-06 09:54:06 +00:00

v4.3.0 build order: Product Surface in eight phases #514

claude-bot referenced this issue

2026-09-11 00:02:30 +00:00

[UX] Wiki redesign — design record #593

claude-bot referenced this issue

2026-11-06 02:02:59 +00:00

Scenes become real objects: campaign-wide, reusable across sessions, buildable before they have cards (the Quest Board half of #689) #1347

No Branch/Tag specified

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

More information is needed

recording

Issue related to the recording system

security

Security hardening / vulnerability work

No labels

Milestone

Clear milestone

No items

No milestone

v4.0.0 - Session Pipeline Accuracy

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#330

Reference in a new issue

Repository

rbrooks/Quest-Board

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns