You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a special component for assigning volunteers built already - used in Mission Control in planning view. We want to keep the business logic the same as that but put it into the mission edit view. Hopefully, this can be (or already is) componentized so it can be reused here.
The organizer needs to be able to:
see how is assigned to a mission
see whether they are tentative or have accepted
unassign a volunteer (up until the mission is started)
suggest a new one (up until the mission is started)
Once a mission is started it should be read-only. That is if MissionState is X, then:
unassigned - editable
tentative - editable,
assigned - editable
started - read only
delivered - read only
succeeded - read only
failed - read only
Per the component, if the volunteer field is changed it should clear volunteerUid field and set tentativeVolunteerUid - thus requiring volunteer to accept it before it moves from tentative to 'accepted'
It should always be possible (whether read-only or editable) for the organizer to see whether the volunteer has 'accepted' or if the mission assignment is still 'tentative'.
The text was updated successfully, but these errors were encountered:
utunga
changed the title
Organizers can view and (somtimes) edit volunteer information on mission edit view
Organizers can view and (sometimes) edit volunteer information on mission edit view
May 17, 2020
Part of the mission edit user story - #431
There's a special component for assigning volunteers built already - used in Mission Control in planning view. We want to keep the business logic the same as that but put it into the mission edit view. Hopefully, this can be (or already is) componentized so it can be reused here.
The organizer needs to be able to:
The fields involved are:
--
Once a mission is started it should be read-only. That is if MissionState is X, then:
unassigned - editable
tentative - editable,
assigned - editable
started - read only
delivered - read only
succeeded - read only
failed - read only
Per the component, if the volunteer field is changed it should clear volunteerUid field and set tentativeVolunteerUid - thus requiring volunteer to accept it before it moves from tentative to 'accepted'
It should always be possible (whether read-only or editable) for the organizer to see whether the volunteer has 'accepted' or if the mission assignment is still 'tentative'.
The text was updated successfully, but these errors were encountered: