This repository has been archived by the owner on Jul 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 58
Reservation Flags #1216
Labels
Milestone
Comments
This can be thought of as addressing the original impetus for #462; namely, the ability to flag reservations with different attribute (such as equipment broken) for more classification options. Note that we might want to figure out a way to generate an "ad-hoc" scope for reservations that match a particular bitmask attribute. |
The |
Oh, there's also information in our wiki about the flags: see here |
And we have a scope that returns reservations with a particular flag as of #462, so that is no longer necessary for this issue |
Updated the issue description with a consolidated to-do list. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2015-10-03
Merged in #1314, consolidating to-do list:
Required:
fined
flagIf possible:
ORIGINAL
#462 implemented a bitmask for miscellaneous boolean values for reservations, which is currently used to flag requests and for an email task. This should be used to mark any issues with the reservation; for example, if it is lost or broken, the reservation should be flagged as such.
This also means adding checkboxes to the check-in form and the archive JS pop up to set these flags.
See here and here for more information on bitmasks.
The text was updated successfully, but these errors were encountered: