-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Asset Notes #63
Comments
This has been done on checkin and checkout. Please make sure to run
after grabbing the latest! |
So when attempting to use action logs to log edit events, I ran into the roadblock that checkedout_to (I'm assuming others are as well) are required fields. The requirements on that might need to be relaxed somewhat so that the action log can be used for more than checkin/checkouts (my next step was being able to just add a generic note, without a check in/out operation) |
That's not currently how the table structure is set up though. It's not meant to be a log notes, just log actions and keep notes with it that may inform about the actions. |
then unfortunately it doesn't solve this ticket; "action log" seems like far too broad (and useful) to just be limited to check in/out. |
For me, custom fields and file uploads (service record invoices, original purchase invoices) and higher priority. Maybe a notes/uploads table combined? |
Didn't know that was on the agenda... But again, under the adage that every line of code is a liability, i think it would be easier to build one history system that's flexible, than try to build one out for each facet of things that change over time (and need to be kept track of). |
Think bug tracker issue commentary; a date/time/user stamped message from a user about a particular piece of hardware. Could be noting a repair, a recurring issue, retirement, etc.
The text was updated successfully, but these errors were encountered: