Asset Notes

[peelman]

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.

[snipe]

This has been done on checkin and checkout. Please make sure to run

php artisan migrate

after grabbing the latest!

[peelman]

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)

[snipe]

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.

[peelman]

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.

[snipe]

For me, custom fields and file uploads (service record invoices, original purchase invoices) and higher priority. Maybe a notes/uploads table combined?

[peelman]

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).