WPI-LNL / lnldb

Getting rid of that 12+ y.o. perl mess.
MIT License
12 stars 12 forks source link

better table views #804

Open pfrunzio opened 1 year ago

pfrunzio commented 1 year ago

what the db would ideally look like: -pre-request Name, client, location, pm, date submitted, date start, services -prospective (formerly incoming) - not approved Name, client, location, pm, ccs, date start, date end, services -incoming (formerly upcoming) - approved Name, client, location, pm, ccs, date start, date end, services -confirmed Name, client, location, pm, ccs, date start, date end, services -needs a crew chief - confirmed+incoming but only the ones without at least one cc for every service Name, client, location, pm, ccs, date start, date end, services -leaving open and closed untouched for now -add pm to all (and customizable fields for all)

pfrunzio commented 1 year ago

events pending billing review should also have pms as a column

benjamin-antupit commented 1 month ago

Try datatables w/django module. Consider this one: https://github.com/pivotal-energy-solutions/django-datatable-view

OR Use Bootstrap Tables to make tables searchable & filterable. But editing with a table might be difficult.

alextannenbaum commented 1 week ago

Better table view, allow ability to add/remove fields, better filtering, "frictonless" editing on fields like event status/VP notes/todos