Skip to content

Milestones

List view

  • Features that we'd like to implement, but that aren't associated with any more specific milestones.

    No due date
    6/12 issues closed
  • Administrators should be able to generate custom reports (essentially, selecting which database columns they want to export). Output in CSV format to avoid vendor lock-in. - Add support for naming and saving common report types (e.g. Admins will request Names/RINs/Balances of all users every semester, so they should be able to configure the report once and run it many times) - Add d3.js visualizations?

    No due date
  • Once we reach feature parity, our next major task will be making it easier for classes and clubs to use the site. For classes: - Students, once added to a class, should be able to flag machine usages as "for a class". - These usages should be billed to a class account instead of the student's personal account. - A student with a class account who has not agreed to the club's membership fee should only be able to use machines for class. - Professors should be able to see an overview of student machine usage. For organizations: - Each organization will be given an RFID token linked to their account.

    No due date
    0/1 issues closed