I took a fairly brief look at it. Seems like its on a good track. I haven't looked enough at the architecture yet to have any comments on that area. I do have a question: if this is using solr facets, will that make it challenging later to extend this to custom fields? And are we compounding complexity by adding filtering to both solr & mongo views? Mongo views were to avoid solr indexing delays, but at some point it might make sense to simplify and drive it all from solr.
Few things I noticed so far: after you filter down on a facet, you don't have any way to change the values for that facet (or clear them). Also when on a milestone view, the facet choices for status aren't correct (at least on my test project). The UI could use some polish, but we can get to that a bit later. --- ** [tickets:#4019] Add an easy way to filter ticket queries by open/closed without knowing Solr syntax** **Status:** code-review **Labels:** 42cc **Created:** Fri Apr 06, 2012 01:04 PM UTC by Patrick Lenz **Last Updated:** Fri Dec 20, 2013 11:35 AM UTC **Owner:** nobody If you search from the "Search Tickets" form in the upper left and get an overwhelming number of results, it often times helps to just weed out either open or closed tickets (depending what you're looking for). I'd love a way to just add that filter with a click instead of redoing the search all over remembering the appropriate Solr syntax and whether or not I need to add `&&`. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
