Require application when creating milestones setting
Problem
Some organisations want to ensure that every milestone created by an applicant or verifier is always linked to a funding application. Previously, the application field in the milestone creation modal was optional, and omitting it would create a "registration entity" type milestone with no application link. This made it harder for administrators to track and manage milestones within the context of specific applications.
How it works
A new boolean organisation setting, Require Application when creating milestones, is available under the Milestones section of the organisation settings page. When enabled:
Client-side validation: The application dropdown in the milestone creation modal becomes a required field. The "Continue" button remains disabled until an application is selected.
Server-side enforcement: If an applicant or verifier submits the milestone creation form without selecting a funding application, the request is rejected and the user is redirected back to the milestones list.
When the setting is disabled (the default), behaviour is unchanged -- applicants and verifiers can still create milestones without selecting an application, resulting in a registration entity type milestone.
UI changes
Organisation settings (show page): A new read-only row appears in the Milestones section showing whether the setting is enabled or disabled.
Organisation settings (edit page): A new enabled/disabled radio button pair appears in the Milestones section for toggling the setting.
Milestone creation modal (applicant and verifier): When the setting is enabled, the application select field enforces selection before the form can be submitted.
Last updated
Was this helpful?