A few ideas - Default fields

Idea created by brandon.miller@samanage.com Employee on May 25, 2016
    Under Consideration
    • brandon.miller@samanage.com
    • Todd Thomas
    • craig.stockman@samanage.com
    • Todd Funasaki
    • 7166025
    • patrick.farrell@york.ca
    • tod.kehrli@accolade.com
    • 3265450

    (Originally posted on 2, February 2015)

    It could be beneficial to be able to remove certain fields from view on the back end of the application if they are not being used.  For instance, if you don't have categories, subcategories, or departments, then having them show up as fields for your technicians to fill out can be a little redundant.  Being able to remove some of the non-mandatory states (On hold or Awaiting input for instance) could also help if you are setting up a basic ticketing system and just want New, Assigned, and Resolved/Closed.


    Also, while I'm thinking about it, it could be beneficial to have an option to set a default in terms of custom forms and fields.  For instance, having a dropdown that defaults to a particular option when creating a ticket on behalf of a customer.

    What problem will this feature solve?: