27 KiB

Raw Blame History

GitHub Project - User Stories Summary

Generated: 2026-01-15 15:40:50 Total Stories: 42 Issues Created: 41

Stories Created

#	Title	Status	Priority	Epic	Effort	Risk	Issue URL
1.1	Database Schema Extension	Draft	Critical	Phase 1 - Foundation	2-3 days	Low	Link
1.2	Core Models Implementation	Draft	Critical	Phase 1 - Foundation	3-4 days	Low	Link
1.3	Authorization Layer Extension	Draft	Critical	Phase 1 - Foundation	2-3 days	Medium	Link
2.1	Cohort Creation & Management	Draft	High	Phase 2 - Backend Business Logic	3-4 days	Low	Link
2.2	TP Signing Phase Logic (High Risk - Prototype First)	Draft	Critical	Phase 2 - Backend Business Logic	4-5 days	High	Link
2.3	Student Enrollment Management	Draft	High	Phase 2 - Backend Business Logic	3-4 days	Medium	Link
2.4	Sponsor Review Workflow	Draft	Medium	Phase 2 - Backend Business Logic	2-3 days	Low	Link
2.5	TP Review & Finalization	Draft	Medium	Phase 2 - Backend Business Logic	2-3 days	Low	Link
2.6	Excel Export for Cohort Data	Draft	Medium	Phase 2 - Backend Business Logic	2-3 days	Low	Link
2.7	Audit Log & Compliance	Draft	High	Phase 2 - Backend Business Logic	2-3 days	Medium	Link
2.8	Cohort State Machine & Workflow Orchestration	Draft	High	Phase 2 - Backend Business Logic	2-3 days	Medium	Link
3.1	RESTful Cohort Management API	Draft	Critical	Phase 3 - API Layer	2-3 days	Low	Link
3.2	Webhook Events for Workflow State Changes	Draft	Medium	Phase 3 - API Layer	2-3 days	Low	Link
3.3	Student API (Ad-hoc Token-Based Access)	Draft	Medium	Phase 3 - API Layer	3-4 days	Medium	Link
3.4	API Documentation & Versioning	Draft	Medium	Phase 3 - API Layer	1-2 days	Low	Link
4.1	Cohort Management Dashboard	Draft	High	Phase 4 - Frontend - TP Portal	3-4 days	Low	Link
4.2	Cohort Creation & Bulk Import	Draft	High	Phase 4 - Frontend - TP Portal	2-3 days	Medium	Link
4.3	Cohort Detail Overview	Draft	High	Phase 4 - Frontend - TP Portal	2 days	Low	Link
4.4	TP Signing Interface	Draft	High	Phase 4 - Frontend - TP Portal	3-4 days	High	Link
4.5	Student Management View	Draft	Medium	Phase 4 - Frontend - TP Portal	2 days	Low	Link
4.6	Sponsor Portal Dashboard	Draft	High	Phase 4 - Frontend - TP Portal	3 days	Medium	Link
4.7	Sponsor Portal - Bulk Document Signing	Draft/Pending	High	TP Portal - Frontend Development	3 days	Medium	Link
4.8	Sponsor Portal - Progress Tracking & State Management	Draft/Pending	High	TP Portal - Frontend Development	2 days	Low	Link
4.9	Sponsor Portal - Token Renewal & Session Management	Draft/Pending	High	TP Portal - Frontend Development	2 days	Medium	Link
4.10	TP Portal - Cohort Status Monitoring & Analytics	Draft/Pending	High	TP Portal - Frontend Development	2 days	Low	Link
5.1	Student Portal - Document Upload Interface	Draft/Pending	High	Student Portal - Frontend Development	2 days	Low	Link
5.2	Student Portal - Form Filling & Field Completion	Draft/Pending	High	Student Portal - Frontend Development	3 days	Medium	Link
5.3	Student Portal - Progress Tracking & Save Draft	Draft/Pending	High	Student Portal - Frontend Development	2 days	Low	Link
5.4	Student Portal - Submission Confirmation & Status	Draft/Pending	High	Student Portal - Frontend Development	2 days	Low	Link
5.5	Student Portal - Email Notifications & Reminders	Draft/Pending	High	Student Portal - Frontend Development	2 days	Low	Link
6.1	Sponsor Portal - Cohort Dashboard & Bulk Signing Interface	Draft/Pending	High	Sponsor Portal - Frontend Development	3 days	Medium	Link
6.2	Sponsor Portal - Email Notifications & Reminders	Draft/Pending	High	Sponsor Portal - Frontend Development	2 days	Low	Link
7.1	End-to-End Workflow Testing	Draft/Pending	Critical	Integration & Testing	3 days	High	Link
7.2	Mobile Responsiveness Testing	Draft/Pending	High	Integration & Testing	2 days	Medium	Link
7.3	Performance Testing (50+ Students)	Draft/Pending	Critical	Integration & Testing	3 days	High	Link
7.4	Security Audit & Penetration Testing	Draft/Pending	Critical	Integration & Testing	3 days	High	Link
7.5	User Acceptance Testing	Draft/Pending	High	Integration & Testing	5 days	Medium	Link
8.0	Development Infrastructure Setup (Local Docker)	Draft	High	Phase 8 - Deployment & Documentation	2 days	Low	Link
8.0.1	Management Demo Readiness & Validation	Draft	High	Phase 8 - Deployment & Documentation	3 days	Low	Link
8.5	User Communication & Training Materials	Draft	High (Blocking - Required Before Development)	Phase 8 - Deployment & Documentation	2 days	Medium	Link
8.6	In-App User Documentation & Help System	Draft (Deferred - Post-MVP)	Medium	Phase 8 - Deployment & Documentation	1.5 days	Low	Link
8.7	Knowledge Transfer & Operations Documentation	Draft (Deferred - Post-MVP)	Medium	Phase 8 - Deployment & Documentation	1 day	Medium	❌ Failed

Quick Reference

1.1: Database Schema Extension

Status: Draft | Priority: Critical | Epic: Phase 1 - Foundation

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/28

User Story: As a system architect, I want to create the database schema for FloDoc's new models, So that the application has the foundation to support cohort management.

1.2: Core Models Implementation

Status: Draft | Priority: Critical | Epic: Phase 1 - Foundation

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/29

User Story: As a developer, I want to create ActiveRecord models for the new FloDoc tables, So that the application can interact with cohorts and enrollments programmatically.

1.3: Authorization Layer Extension

Status: Draft | Priority: Critical | Epic: Phase 1 - Foundation

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/30

User Story: As a system administrator, I want the authorization system to support FloDoc roles and permissions, So that users can only access appropriate cohort management functions.

2.1: Cohort Creation & Management

Status: Draft | Priority: High | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/31

User Story: As a TP (Training Provider) administrator, I want to create and manage cohorts with all their configuration details, So that I can organize students into training programs and prepare them for the signature workflow.

2.2: TP Signing Phase Logic (High Risk - Prototype First)

Status: Draft | Priority: Critical | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/32

User Story: As a TP administrator, I want to sign the first student's document and have that signing replicated to all other students in the cohort, So that I don't need to sign each student's document individually, saving time and eliminating duplicate sponsor emails.

2.3: Student Enrollment Management

Status: Draft | Priority: High | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/33

User Story: As a TP administrator, I want to manage student enrollment in cohorts and bulk-create student submissions, So that students can access their documents to complete after TP signs.

Status: Draft | Priority: Medium | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/34

User Story: As a Sponsor, I want to review all student documents in my cohort and sign them in bulk, So that I can complete the verification workflow efficiently.

2.5: TP Review & Finalization

Status: Draft | Priority: Medium | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/35

User Story: As a TP administrator, I want to review the sponsor-verified submissions and finalize the cohort, So that the entire 3-party signature workflow is completed and documents are ready for archival.

2.6: Excel Export for Cohort Data

Status: Draft | Priority: Medium | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/36

User Story: As a TP administrator, I want to export cohort enrollment data to Excel, So that I can perform additional analysis or reporting outside the system.

2.7: Audit Log & Compliance

Status: Draft | Priority: High | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/37

User Story: As a TP administrator, I want comprehensive audit logs of all cohort workflow activities, So that we can demonstrate compliance and trace any issues.

2.8: Cohort State Machine & Workflow Orchestration

Status: Draft | Priority: High | Epic: Phase 2 - Backend Business Logic

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/38

User Story: As a system, I want to manage cohort state transitions and workflow enforcement, So that the 3-party signature workflow follows the correct sequence and prevents invalid operations.

3.1: RESTful Cohort Management API

Status: Draft | Priority: Critical | Epic: Phase 3 - API Layer

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/39

User Story: As a TP administrator or external system integrator, I want to create, read, update, and delete cohorts via REST API, So that I can automate cohort management and integrate with other systems.

3.2: Webhook Events for Workflow State Changes

Status: Draft | Priority: Medium | Epic: Phase 3 - API Layer

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/40

User Story: As a TP administrator, I want webhook notifications for all cohort workflow events, So that external systems can react to state changes in real-time.

3.3: Student API (Ad-hoc Token-Based Access)

Status: Draft | Priority: Medium | Epic: Phase 3 - API Layer

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/41

User Story: As a student with a cohort link, I want a simple token-based API to access and complete my documents, So that I can fulfill my requirements without account creation.

3.4: API Documentation & Versioning

Status: Draft | Priority: Medium | Epic: Phase 3 - API Layer

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/42

User Story: As a developer integrating with FloDoc, I want comprehensive API documentation and stable versioning, So that I can build reliable integrations without breaking changes.

4.1: Cohort Management Dashboard

Status: Draft | Priority: High | Epic: Phase 4 - Frontend - TP Portal

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/43

User Story: As a TP administrator, I want a dashboard to view and manage all cohorts, So that I can monitor the 3-party workflow at a glance.

4.2: Cohort Creation & Bulk Import

Status: Draft | Priority: High | Epic: Phase 4 - Frontend - TP Portal

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/44

User Story: As a TP administrator, I want to create new cohorts and bulk-import students via Excel, So that I can efficiently onboard large groups without manual data entry.

4.3: Cohort Detail Overview

Status: Draft | Priority: High | Epic: Phase 4 - Frontend - TP Portal

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/45

User Story: As a TP administrator, I want to view detailed information about a specific cohort, including student list, progress status, and document workflow, So that I can monitor and manage the cohort effectively.

4.4: TP Signing Interface

Status: Draft | Priority: High | Epic: Phase 4 - Frontend - TP Portal

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/46

User Story: As a TP administrator, I want to sign the first student's document and have it automatically replicated to all other students, So that I can sign once instead of signing each student's document individually.

4.5: Student Management View

Status: Draft | Priority: Medium | Epic: Phase 4 - Frontend - TP Portal

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/47

User Story: As a TP administrator, I want to view and manage individual student details, including their document status and uploaded files, So that I can track student progress and troubleshoot issues.

Status: Draft | Priority: High | Epic: Phase 4 - Frontend - TP Portal

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/48

User Story: As a Sponsor, I want to access a dedicated portal where I can review and verify all student documents for a cohort, So that I can sign once for the entire cohort instead of signing each student individually.

Status: Draft/Pending | Priority: High | Epic: TP Portal - Frontend Development

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/49

User Story: As a Sponsor, I want to sign once and have that signature applied to all pending student documents, So that I don't need to manually sign each student's documents individually.

Status: Draft/Pending | Priority: High | Epic: TP Portal - Frontend Development

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/50

User Story: As a Sponsor, I want to see real-time progress tracking with clear visual indicators of which students have completed their documents and which are still pending, So that I can monitor the signing workflow and know exactly when to proceed with bulk signing.

Status: Draft/Pending | Priority: High | Epic: TP Portal - Frontend Development

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/51

User Story: As a Sponsor, I want to renew my access token if it expires while I'm reviewing documents, So that I can complete my signing workflow without losing progress or being locked out.

4.10: TP Portal - Cohort Status Monitoring & Analytics

Status: Draft/Pending | Priority: High | Epic: TP Portal - Frontend Development

Issue: https://github.com/NeoSkosana/floDoc-v3/issues/52

User Story: As a Training Provider, I want to monitor all cohorts with real-time status updates and analytics, So that I can track progress, identify bottlenecks, and manage my document signing workflows efficiently.