Correct attendance and group familiarity without erasing history #65
Labels
No labels
area/backend
area/frontend
area/tooling
kind
build
kind
chore
kind
ci
kind
docs
kind
feat
kind
perf
kind
test
size
l
size
m
size
s
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#67 Show group familiarity and apply the previous-tester admission setting
viacheslavshuka/quorum
#68 Generate alphabetical tester acknowledgment lists
viacheslavshuka/quorum
#69 Restrict participation and organizing capabilities with reversible expiry
viacheslavshuka/quorum
#71 Show tester and organizer activity rankings from recorded participation
viacheslavshuka/quorum
#72 Cancel upcoming tests and stop running tests through explicit controls
viacheslavshuka/quorum
#48 Give operator-appointed moderators a private report queue
viacheslavshuka/quorum
#62 Close registration at start and complete ended tests automatically
viacheslavshuka/quorum
Reference
viacheslavshuka/quorum#65
Loading…
Reference in a new issue
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?
Automatic completion assumes confirmed testers attended. Organizers need to correct no-shows, departures, and partial attendance while keeping the source and consequences reviewable.
Acceptance criteria
Validation
Correct a tester with two familiarity sources, mark one test never held, and assert the other source survives. Check partial attendance inside a single block, duplicate correction writes, notification contents, and updated credit totals. Assert that rejected tester-side writes preserve session records and audit history.
Dependencies
Related work