...
Draft games need to be shared to associations who need to be able to view all their draft games in one place regardless of schedule
Draft games must be in their own model to make this relation feasible
Draft games may impact availability as soon as they’re scheduled even if not yet “published”
This setting currently exists
If a draft game is rescheduling an existing game this should be clearer
Currently this matches on game number
More flexibility on draft creation flows
Currently it’s a rigid info/teams/review/publish flow, certain options may require more details for improved UX
Should be possible to partially publish some draft games when they’re ready
e.g., one association is done early but others aren’t ready yet
Future (Out of scope)
Total games per round
Provide a matrix to show how many games each team plays against each other to produce a set of games to be scheduled
Date scheduling in calendar
Scheduler must produce dates to be able to use the calendar currently
Rescheduling
Teams need to be able to propose changes to scheduled games by other team and/or league approval
...
Would be nearly identical to Game, with additional properties:
Property | Type | Description |
|---|---|---|
gameId | number | ID of game being updated. This would be automatically filled in based on the game number when generating/uploading games and would be used when using the (future) rescheduling function |
round | number | Not 100% sure if this is still desired |
ScheduleTeam
Same as before, with additional properties:
Property | Type | Description |
|---|
ScheduleTeam
...
order | number | This is used to maintain schedule balance when generating additional games. Adding a scheduleteam would automatically use the next order. Schedulers would be able to adjust the order in the UI |
UX
Draft creation will no longer be a single page workflow, since games will no longer be within a draft. Instead, draft creation behaves more like an import modal.
...