Skip to content

User Requests and Ideas

Peter Flanigan edited this page May 25, 2017 · 33 revisions

Suggestions for consideration (not necessarily a feature requests)

Suggestions that have been implemented have been removed. Closed issues can be seen here

  1. Distinct certifications for bike types: Deauville / Pan / FJR, and only allow those assignments

    • Response: Need more information. We could add courses / certification for bike types. We do not have a way of differentiating vehicle subtypes. Add certificate type to vehicle record. Rider requires vehicle certificate to get that type of vehicle assigned.
  2. Can’t really explain it, but when there is a button in the app I think that better give the feeling that “this is working as it should, there is an error here, but it is for a specific reason, there isn’t anything wrong with the app, it is you.”

    • Response: It already does this. There are growler like notifications in the bottom right corner which let you know when an action was performed successfully. The error messages let you know when something has gone wrong (but not what went wrong since the messages were dumbed down).
  3. Auto-populate the "old password" field in password reset email

    • Response: But no, it's a security thing
  4. Add more reports to support exports for charts

  • Response: Need more information. Need to see the charts in question so that we can work out the required input format, but otherwise very doable.
  1. In call logging, when you go back to edit an entered stage, it would be more intuitive if there was a bit of text saying "edit" or "update" rather than clicking on the persons name. It wasn't clear to me at all that you could edit an entry after the fact.
  • Response: The mouseover help text has been changed to include the word "edit". Elsewhere in the application "edit" links do appear in the same context so there is prior art. The call logging, which is newer code, is different for aesthetic reasons. It's providing a less cluttered look than older screens with the "edit" link. Throughout the application (in the dark theme), if it's coloured yellow then you can probably click on it and it may have mouseover help text as well.
  1. Can we make a training videos with CamStudio. One for bike riders and drivers, one for controllers and one for the rota manager showing her how to use the application to assign vehicles to slots and events?
  • Response: Excellent suggestion. This will be very useful going forward when it comes to teaching new members how to use the application
  1. When one mouseover's a page menu link, the info box that pops up has a red border making it look like a bit like an error / warning message instead of an info message
  • Response: The red border is used around all dialogs and as a contrast colour throughout the application. Yellow implies a link that you can click on so making the border yellow would make no sense
  1. The small red letter within the month rota representing vehicle requested - its far too vivid.
  • Response: True dat. Someone should create an issue about it
  1. A news ticker of some sort, visible to logged in users, where some role (new ticker_writer role perhaps) can add "breaking news" - "Bikes grounded due to high winds" - that sort of thing, that scrolls across the top of the page. Probably ought to have a TTL so that the message can't be forgotten and let up indefinitely.

  2. Ad-hoc messages/information screen at login. If we wanted to announce a future event (site will be offline for maintenance at 9pm for instance) a simple way of doing so that doesn't look like any other information page would be useful - a popup dialog when you log in for instance. Or a contrasting colour strip along the top of the page (a bit like the ticker above I guess, only static text.

  3. Calls to our on call number generate notification email to a mailbox. It would be useful to the controllers if we could display the call history by scraping these emails - connect to an imap account, read the latest emails and parse out the calling number and time, and display those data on a controller-accessible page in the app.

Clone this wiki locally