-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: "History" details are being overwritten when a modification to a booking is submitted. #658
Comments
@ss12430 this is a bug (Modifications are being treated like Edits in so far as the timestamp of the modification is being written to all statuses) and a feature request (you want a "History" with more granular details) which is a much heavier lift. "History" is a bit of a misnomer in so far as it only represents progression along a linear sequence of changes to status, not every change that's made to a booking. splitting this into two cards (the bug and the feature request). we'll need to revisit which of the current feature requests with priority HIGH can be downgraded in terms of urgency. |
See “History” section in screenshot below.
This booking was approved on 3/20. On 3/21 at 2:29pm Erik made an edit to the end time of the reservation, and the timestamp for Requested, Pending, and Approved was overwritten to the time that the modification was made. Under “User” it still has the reservation holder's email which could make it appear that the reservation holder made the edit rather than Erik. Would like a way to add to the history rather than write over it, like adding a 4th line when an edit is made. Should also talk about what happens with a small edit like this, versus a reservation holder editing something that causes the request to go through the approval process again.
The text was updated successfully, but these errors were encountered: