-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Mandatory data fields for completed or cancelled engagements #1243
Comments
We should do this in 2 steps. Step 1: make location and at least one task mandatory (for past or future engagements). Preferably in candidate and candidate 2.1 Step 2: Make the engagement details mandatory in candidate-2.1 |
@gjvoosten An additional mandatory field for cancelled engagements should be one of the six cancellation reasons. |
That is already the case, and will not change. But I'll make it explicit in the description. |
Update mandatory data fields for completed or cancelled engagements
The requirements owners have decided the following 10 data fields should be required for a completed engagement:
This would leave the following four data fields optional for a completed engagement:
For a cancelled engagment, required fields are:
I believe currently the following six data fields are optional:
The text was updated successfully, but these errors were encountered: