Mass offering change reassess all applications that have reached assessment.
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
As all users we want a mass offering change to not cancel applications one they have been assessed. So that assessed applications do not need to be completely redone for each mass offering change
**Acceptance Criteria**
- [ ] Change it so that when a mass offering change is approved, any status from assessment forward get reassessed.
- [ ] Update to align with pir not repeat change
**Additional Context**
In current state only completed applications get reassessed and all other applications get cancelled. We would like this changed to align with out sequential reassessment logic that uses the assessment date as the validation date so that all applications once assessed are maintained and not cancelled in these scenarios.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.