...
SID: Create a league/tournament, sync to Play (done)
SID: Add organisations to the league/tournament, sync to Play (missing)
SID: Create competitions, sync to Play as schedules (missing)
SID: Add teams to the competition, sync to Play (missing)
Play: Create games (done)
Models
SID API | SID properties | Play Model | Notes |
---|---|---|---|
affiliated-organisations |
| OfficeMember |
|
competitions |
| Schedule |
|
competition-teams |
| ScheduleTeam |
|
UX
Arrive in Play, all you need to do is create games. ✨
...
How to determine when to limit member/schedule/team creation in Play? Should this be an office flag?
Implementation
Add externalId to OfficeMember, Schedule, ScheduleTeam
...
OfficeMember
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
OfficeMember: Add seasonId, categoryId
This has a similar problem with roster members as SID has a member per position, where Play groups as an array, so we need multiple rows to track the externalId correctly and figure out the UX
Authorization will be affected by seasonId/categoryId change
Webhooks
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|