Warn if milestone due date is in the past or far in the future

Problem

When setting up milestones in either the milestones batch wizard or the contracts wizard, admins could accidentally enter a due date that is in the past or unreasonably far in the future (e.g. a typo resulting in a date decades away). There was no feedback to alert them to a potentially incorrect date.

Solution

A non-blocking warning message is now displayed below the due date field whenever a milestone is saved with a date that appears incorrect. The warning does not prevent the admin from saving — it simply draws attention to the value so they can verify it is intentional.

How it works

After a milestone's due date is autosaved, the system checks the date:

• If the due date is in the past, a warning is shown: "Warning: this due date is in the past"

• If the due date is more than 5 years in the future, a warning is shown: "Warning: this due date is more than 5 years in the future"

• Otherwise, no warning is displayed

The warning appears inline below the due date field and clears automatically when the date is corrected.

UI

A yellow/orange warning message appears directly beneath the due date input field in both:

• The milestones batch wizard (milestone batches)

• The contracts wizard milestones step (contract milestones)

The warning is informational only and does not block saving or progressing through the wizard.