Managing phases is an important part of the admin process, to correct issues, extend, open phases that were skipped by autopilot, etc...
In anticipation of having new features in the system-admin app for phase management, I'd like some new endpoints added to the challenge API:
GET /v6/challenges/{challengeId}/phases
- Returns all phase information for that challenge
GET /v6/challenges/{challengeId}/phases/{id}, where id is the id value of the phase
- Returns the information for a single phase associated with the challenge
PATCH /v6/challenges/{challengeId}/phases/{id}, where id is the id value of the phase
- Partially update a phase. For instance, if I only want to open the phase, I could give body:
{"isOpen":true}
- Any combination of phase object values should be accepted and validation should occur (end date can't be before start, duration can't be negative,
phaseId has to match a known phase, predecessor must exist, etc..)
DELETE /v6/challenges/{challengeId}/phases/{id}, where id is the id value of the phase
- Deletes a phase and recalculates the predecessors. This will mainly be used to delete any added phases that aren't needed. For instance, if we want to rewind a challenge and remove the
Post-Mortem phase and reopen submission, which is something I had to do recently.
Managing phases is an important part of the admin process, to correct issues, extend, open phases that were skipped by autopilot, etc...
In anticipation of having new features in the system-admin app for phase management, I'd like some new endpoints added to the challenge API:
GET /v6/challenges/{challengeId}/phasesGET /v6/challenges/{challengeId}/phases/{id}, whereidis theidvalue of the phasePATCH /v6/challenges/{challengeId}/phases/{id}, whereidis theidvalue of the phase{"isOpen":true}phaseIdhas to match a known phase, predecessor must exist, etc..)DELETE /v6/challenges/{challengeId}/phases/{id}, whereidis theidvalue of the phasePost-Mortemphase and reopen submission, which is something I had to do recently.