CTF-1305: Submission History¶
Statement¶
The system should record and display all flag submission attempts. Organizers shall be able to view, search, and filter all submissions across an event (correct, incorrect, by participant, by challenge, by time). Participants shall be able to view their own submission history per challenge if the event configuration permits. The system shall display submission type (correct/incorrect), the provided value, timestamp, and the submitting participant.
Rationale¶
Submission history is essential for organizers to detect cheating, debug flag issues, and understand participant behavior. Participant self-viewing helps them track their own progress and avoid resubmitting the same incorrect answers. Organizers need filtering by type (correct/incorrect), participant, challenge, and full-text search for effective event management. (CTFd provides a full submissions admin interface with similar capabilities.)
Traceability¶
- IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/admin/(CTFSubmissionAdmin - Organizer view/search/filter of all submissions) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/models/(CTFSubmission model - Records all submission attempts with correctness, flag, timestamp, participant) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/views/(challenge_detail view - Participant views own submissions per challenge) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/views/(api_submissions - Participant API to view own submission history) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/views/(admin_participant_detail - Organizer views participant submission history) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/services/submission.py(Submission service - get_participant_submissions, get_challenge_submissions, get_correct_submissions) - IMPLEMENTS → GITHUB_ISSUE
539(Issue #539 - automated coverage and Ground Control TESTS trace links for active CTF requirements)