...
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 reschedules an existing game this should be clearer
Currently this matches on game number transparently
Need 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 as they’re ready
e.g., one association is done early but others aren’t ready yet
...
Out of scope
...
These issues are not specifically addressed by this proposal and will be addressed in other proposals. This proposal creates a framework to resolve these issues.
Provide a matrix to show how many games each team plays against each other to produce a set of games to be scheduled
Scheduler must produce dates to be able to use the calendar currently
Teams need to be able to propose changes to scheduled games and need approval by other team and/or league a
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. This applies to entering the options before games are produced (as in the first two steps currently).
...
This can behave exactly like existing import modals
Will still need to reuse logic of matching teams and arenas
When matching teams, limit to existing ScheduleTeams
...
Manual
This just becomes creating a single draft game at at time, so there’s no special flow necessary as the only configuration was a starting game number
...
Existing unpublished drafts to be converted to draft games
Cleanup flags, UI and deprecate API
Planner
...
| View file | ||
|---|---|---|
|
...