Sodium Filters / Views



  • A couple of observations --

    • When none of the Ticket Status checkboxes are checked, only open tickets are shown. I would expect all tickets to be shown.
    • Need to be able to update / remove a View. Currently get the following when I try to Save Filter As View with an existing name

    0_1505357150689_870d71f1-2d29-498e-969b-46cf1f730df2-image.png



  • @danp said in Sodium Filters / Views:

    A couple of observations --

    • When none of the Ticket Status checkboxes are checked, only open tickets are shown. I would expect all tickets to be shown.
    • Need to be able to update / remove a View. Currently get the following when I try to Save Filter As View with an existing name

    0_1505357150689_870d71f1-2d29-498e-969b-46cf1f730df2-image.png

    1. Well look at that on the first point. Will fix that today.
    2. Valid points. Already on the list of things to do. Hopefully will get to this today as well 🙂


  • @quixoticjeremy said in Sodium Filters / Views:

    @danp said in Sodium Filters / Views:

    A couple of observations --

    • When none of the Ticket Status checkboxes are checked, only open tickets are shown. I would expect all tickets to be shown.
    • Need to be able to update / remove a View. Currently get the following when I try to Save Filter As View with an existing name

    0_1505357150689_870d71f1-2d29-498e-969b-46cf1f730df2-image.png

    1. Well look at that on the first point. Will fix that today.
    2. Valid points. Already on the list of things to do. Hopefully will get to this today as well 🙂

    First point has been resolved and will be in the next release. Looking to get to the second point here in a little bit.



  • on that subject... sorta.

    Oops

    0_1505405406872_2017-09-14 12_08_40-Clipboard.png



  • @quixoticjeremy Are there plans to allow for specifying a "default" view, configurable by the end-user?



  • @danp said in Sodium Filters / Views:

    @quixoticjeremy Are there plans to allow for specifying a "default" view, configurable by the end-user?

    Most of this is going to be revamped anyways and likely we will include more features such as this.



  • Long term, as Jeremy implies, loads of filters and views are expected, everywhere in the system. It's not at the top of the list, but it gets higher and higher all of the time as it impacts a lot of basic usability. The system is heavily designed around filters and views being key components of how it all works, both user accessible and behind the scenes.

    For example, we want to easily support use by normal users, individual companies, consultants and MSPs. But we don't want to the system to actually work differently, just look different for different people. For example, individual home users likely don't even want to know that there is ticketing. But an MSP might want is very much in the forefront. It will be a view engine making that all possible.


Log in to reply