...
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).
...
Once the information from the draft modal is filled out, draft games are created and they’ll be available in cards on the schedule, office and teams pages.
...
The current schedule info step is split into multiple steps for matchups and scheduling in the modal
Starting game number input is no longer necessary as drafts will not use a sequence until the games are published
Need to add a previous round input so that the scheduler can continue schedules as usual
This already exists, but isn’t exposed in the UI. It’s automatically populated based on the “previous draft” input, so this will be replaced with a previous round input.
🚩 Critical for PCAHA. Need to check if it’s feasible for their schedulers to use this instead of selecting the last league, or if we need to infer from DraftGamesHelper text should show the latest used round in DraftGames if applicable
ScheduleTeams are now the source for generating the schedule, replacing the teams step
Order matters in team selection. An order will be added on ScheduleTeams so it can be easily reused. Otherwise, the teams step just duplicates the schedule’s teams tab
We’re able to add more context about number of games produced in the helper text of certain inputs. Originally this wasn’t entirely certain as the teams step came after
When specifying game per team, limit the total games to even numbers to prevent unbalanced schedules
Cross group schedules
Selecting two groups will produce a cross-group schedule
Previously you would select no group then select the team/group in the teams step. This no longer exists, so you need to specify the groups that will be crossed
Two possible implementations:
groupId/groupIdsorgroupId/crossGroupId. This is just as an API since options are no longer persistedIdeally it's possible to select two groupIds within the same group input, but it could be better UX to just introduce a cross-group switch that shows another group input Creating a draft would need you to select a
groupIdwhere applicable. For cross-group, provide a switch input that reveals acrossGroupIdgroup input for the cross group to help enforce the notion that you’re only crossing two groups
Game numbers are pulled from the sequence of the home team group
Resulting games do not have a group associated to them, existing logic around stats does not change
...
Uploaded
This can behave exactly like existing import modals
Will still need to reuse logic of matching teams and arenas
...
Property | Type | Description |
|---|---|---|
updatedGameId | number | Optional. ID of game being updated or the resulting game that was published 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 | Optional. Not 100% sure if this is still desired |
isShared | boolean | Grants access to |
sharedAt | datetime | When the game was shared |
sharedUntil | datetime | When sharing access expires |
isPublished | boolean | Acts as |
publishedAt | datetime | When the game was published |
...
Modal to create draft games one by one via the new DraftGame card
Select multiple games to publish, share, or delete
...
Generation
| Status | ||
|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Move the game analysis logic into a library and accessible through the API
...
|
Create a stepper modal that mimics the existing cards
New
POST /schedules/:id/generateAPI would accept the parameters and create draft games
Import modal
| Status | ||
|---|---|---|
|
...
Follow the existing importers to parse a file
This would import as draft games as well as schedule teams
Should we provide an option to publish directly?
...
Analysis dialog
| Status | ||
|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Create a stepper modal that mimics the existing cards
...
|
Move the game analysis logic into a library and accessible through the API
Provide an analysis dialog on the schedule page
Release
| Status | ||
|---|---|---|
|
Existing unpublished drafts to be converted to draft games
Cleanup flags, UI and deprecate API