#301: Custom query: tickets that no longer match the query should move out of
the
main list
-------------------------+-------------------------
Reporter: gjm | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone: Unscheduled
Component: dashboard | Version:
Keywords: |
-------------------------+-------------------------
I have heard a number of people complaining that they have to click
refresh to get rid of tickets that no longer match a custom query. This
may be particularly annoying because of cases where they themselves have
just performed the modification that causes the ticket not to match.
I would suggest that the opposite point of view is equally valid - it is
good to be able to see the set of tickets that used to match with the
updated fields (as we do now) particularly in cases where the viewing user
did not make the change. However, it would be very helpful to make it a
lot clearer that these tickets are no longer matching.
There may be many ways to achieve this but for the moment I will suggest
that tickets that no longer match could move to a second list beneath
those that do match.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/301>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
