New Ticket

TICKET_CREATE privileges are required to perform this operation. You don't have the required permissions



Login Close


Custom query: tickets that no longer match the query should move out of the main list

Ticket #301 Assigned to nobody, last modified 5 years ago

Details

Reporter gjm
Keywords
Type enhancement
Status new
Priority major
Product BHD
Milestone Unscheduled
Component dashboard
Version
Cc

Description

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.

Note: See TracTickets for help on using tickets.

jdreimann

I'd like to see AJAX used more throughout Bloodhound really :-)

olemis

Replying to jdreimann:

I'd like to see AJAX used more throughout Bloodhound really :-)

In order to get there we need to think first of adding something like RestOnTracPlugin so as to have ubiquitous access to Trac via REST-ful web services . Then upgrade widgets accordingly (... and make them smart to detect REST API availability , btw ;)

gjm

Given the comments so far, I am not sure whether the point has been missed. This is not strictly about ajax or widgets, both of which probably deserve their own tickets.

rjollos

The issue has been reported in trac:#9006.