User:Ryan52/todo

new todo list

• #14227 Fix docs on how to install FGdb
• #12482 ease recording hours under multiple types on a given day
• #19348 csv output on searches
• #19190 emails get held up (and released)
• #21768 rootmail borked on several systems
• #21983 eliminate old line item code
• #21466 Certificates of destruction / data destruction verification
• General_scheduling_application#Remaining_Todos

not fgdb

• User:Ryan52/maintenance
• old ASS
  • #16697 RT requires multiple logins
  • #17664 make diskless xterm default font size bigger
• disktest
  • #19172 Reading SMART device error log for HDD testers
• keyboard tester
  • #15784 Newfangled keyboard tester addition request/issues
  • #16161 additional function keys (F13 - F16) as well as the volume/eject keys to (volume up/down/mute keys)
  • #16164 screenshots of each layout and the settings screen

fgdb

• #19495 Extracting Info from Database
• #19360 search for store credits
• #19348 csv output on searches
• make store people happy with store credits
  • make a search for store credits, not gizmo returns, and associate store credits with contacts, so they can be searched for
• fix up the worker type editing interface
  • fix dedupping
  • click on a date or worker_type in old records should put it into the form
  • make it ajax
  • check that I didn't break anything with the fix for #18319
  • fix odd bug with leaving a NULL in the end date in the middle that richard reproduced. steps:
    • set them to be "nother" from point A to C.
    • set them to be "collective" from point C to point D.
    • add in an inactive that goes from point B to point C, between the two.
• reports for taxes and workers comp
• #17796 database - Committed Hours & PTO
• #18316 graphic reports are resource hogs
• #18266 default the individual report and logging staff hours forms
• #17932 tricky to log 0 hours when the schedule expects hours
• use store credit like things for gift certificates
• link to old system IDs on the systems page as well
  • #17231 "current" system ids
• get fgdb.rb able to be set up by new freegeeks and new coders
  • #15523 fgdb can't be set up from scratch atm (broken devel data)
  • #14227 Fix docs on how to install FGdb
• cashier code enhancements
  • #16671 ask for cashier code on destroy
    • want to redo destroy in fgdb anyway
  • #16673 eleminate cashier_created_by?
  • #15498 should not recheck the same cashier code
  • #18046 cashier code on disbursements?

more fgdb

• #17255 overtime report
• #17031 integrate meeting-minder functionality into skedjulnator
• #14861 swap computers (tech support)
• I WANT A TEST SUITE
• db cleanups
  • gizmo_types.effective_on has a silly default
  • workers.contact_id needs to be unique
  • users.contact_id needs to be unique
  • flatten contact_method_types (add a category)
  • created_at should be NOT NULL
• changes to the contact widget
  • need to think this through.
  • should take these tickets into account:
    • #13061 auto search for contacts when creating a contact
    • #14840 contact search kinda sucks
    • #14827 FGDB: force search on create
    • #14828 FGDB feature request #2
    • #15034 add show more button on contact search
• fix up form_has_not_been_edited
  • #15921 form_has_not_been_edited isn't called on edit links, I think
  • #15922 form_has_not_been_edited shouldn't be called on destroy
• #16108 gizmo_types with same name and different effective date ranges should act sanely in reports

junk

• go through remaining trac tickets:
  • fgdb's are emptied already
  • skedjulnator tickets
• old TODO list
• has_many use :autosave for some things
• release utilities
  • get continuation to work with multiple branches
  • get continuation running with test-migrate
  • the auto-update script is connected to my home dir (because of the devel checkout), but it shouldn't be.
    • use multiple working copies from the production checkout: http://kerneltrap.org/mailarchive/git/2007/10/11/335637
      • I have some magic that does this that I use for myself
    • or just create a dbadmin user on arik
      • benefit of possibility of having a key connected to devo.
    • update Committing to FGdb after that.
  • I want all changes on a release_X.X.X branch (after the initial branch) to get their own tag. this would involve running ./script/mini-release (new script?) when making a direct change, and this would affect the output of ./script/version. mini-release would also close the ticket(s) (by pushing the tag, I guess). also, this would mean that pushes on release_X.X.X branches wouldn't close the tickets. this would also affect the changelog workflow probably.