For change requests that are repeated on multiple days, it is currently only possible to either cancel all the repetitions, or edit the request's dates/ weekdays to avoid an event.
It should be possible to skip (in effect cancel) one of these repetitions, without having to cancel or otherwise edit the entire repeated request, perhaps by adding to the database a list of dates to skip. It should be possible to add to this list by selecting a 'skip' button on the Manage Events page, and to manage the list within the events wizard. We will also need to add a cancel button to the edit event wizard, to retain the option of cancelling the entire repeat request.
Technical note: The alternative way of handling a repeat request would be to have it spawn and save all its repetitions as individual requests in the db, which would allow for cancelling them in the normal manner. This was not chosen as it then becomes very problematic to edit the repeat request, as any changes would need to propagate to its spawned events (including potentially deleting and creating new ones), which could have been edited or cancelled independently in the meantime.
For change requests that are repeated on multiple days, it is currently only possible to either cancel all the repetitions, or edit the request's dates/ weekdays to avoid an event.
It should be possible to skip (in effect cancel) one of these repetitions, without having to cancel or otherwise edit the entire repeated request, perhaps by adding to the database a list of dates to skip. It should be possible to add to this list by selecting a 'skip' button on the Manage Events page, and to manage the list within the events wizard. We will also need to add a cancel button to the edit event wizard, to retain the option of cancelling the entire repeat request.
Technical note: The alternative way of handling a repeat request would be to have it spawn and save all its repetitions as individual requests in the db, which would allow for cancelling them in the normal manner. This was not chosen as it then becomes very problematic to edit the repeat request, as any changes would need to propagate to its spawned events (including potentially deleting and creating new ones), which could have been edited or cancelled independently in the meantime.