Open d-tamm opened 2 years ago
Right now it is unclear when things are saved. When i change the times of an own booking as an admin, the change is confirmed without clicking the save button. Clicking the save button would only update consent and contact data.
All user input in the booking flow could be saved in the session rather than in db. This is specially true for accepting and denying resources, but could also replace the booked item's lowest state level.
Right now it is unclear when things are saved. When i change the times of an own booking as an admin, the change is confirmed without clicking the save button. Clicking the save button would only update consent and contact data.
This seems to be fixed now.
The design choice to use the same interface for initial booking and for handling bookings by administrators has its drawbacks and makes the interface confusing for admins. It could be better to have a separate interface for administration. Use ajax extensively (#298), and make clearer how the workflow is supposed to be (#321).