nicolasgomollon/htla-inventory

htla-inventory's Issues

User Authentication

Location-based reports

Mircea wants to be able to run all the reports by each location.

Capistrano deployment

Capistrano deployment doesn't actually work which is rather frustrating.

computers can be assigned to multiple students

RepairOrders can't be updated/closed

You get a form error "activities is invalid" when you try to update or close a repair order.

Prettify templates

Reports

An extensible interface would be nice, but for now just creating some basic reports to help find things like the number of broken computers etc. is all we need. With sorting by locations.

Additionally all of these reports should also be exportable as CSV.

Removing computers from the Inventory

We need a way to remove computers that we no longer have from the active inventory.

How do we handle this? Do we actually delete the records? (I don't like the data integrity of that) Do we set a 'salvaged' flag? How do we make sure only privileged users can do it?

Bill payment

There is currently no way to actually pay for bills.

Rubify controllers

Most of the controllers are using horrendous hacked together code that I don't want anyone to see ever. This stuff needs to get DRYed.

See:

• Admin::ComputersController
• Admin::ComputerOwnershipsController
• Admin::ComputerTemplatesController
• Admin::RepairOrdersController
• and more! (as I find them)

Implement Repair Orders and Billing

Repair Orders represent work that needs to be done on a computer to restore it to working order, and billing represents the costs for that work (parts + labor).

Improve Ownership creation interface.

The ComputerOwnership interface is atrocious because there's not really a good way to save all that state while you search for a computer or student (because obviously only one of those can be filled in at a time).

Location "tracking"

Mircea would like to have some sort of ability to track the location of a laptop, meaning roughly whether it's on hand with the IT Department or with a student.

Generic description of "computer problems"

There are a lot of problems that come up that don't fit in any good hardware category, the Computer model should have a field to handle these weird problems.

You can create repair orders with no description

You can create repair orders and activites without a description, and then you can't delete them, this is kind of annoying.

Front-end user interface

View for students to see status of account.

Search in Navbar

Certain workflows are going to be a lot faster if computer search is possible from the navbar.

View "all" items

Currently there is no way to see all the students or all of the computers. Mircea wants this.

reports#partsview multiple defects/locations search

Mircea wants reports#partsview extended so that you can search by multiple defects and multiple locations.

User Import

reports#assigned does not list student name

reports#assigned does not list the name of student the computer is assigned to.

Redo "Templates" interface.

Everything about the ComputerTemplates interface is ill-conceived, it needs some javascript magic to make it usable.