Filter log screen

Example of exposed filters implemented at http://qa.scratch.drupal.org/pifr/log ... looking for feedback.

Hi @jthorson,

I have just had a look at this, and confirm that the filters are functional as expected.

There are a couple of things that would really help usability though.
- Testbot ID - considering that there are generally only ~4 testbots online at once, can this be a drop down?
- Type - again, could this be a drop down? (Hopefully based on words not numbers?)
- Title - if possible, I think the most usable would be a textbox with autocomplete (and can probably just be called "Title" to match the table). I don't know how much of a performance drag this would be?

In terms of the order, would it be worth putting the Type before the Title? (To match the table)

Is there any way of having a filter by project? That would enable someone to see the branch + patch tests for a project of interest.

I don't mean to come back with lots of comments! Even as is on scratch, it'll be a great help!

Currently, the qa.scratch mockup is just using exposed views filters to expose the options ... is there an extension which will allow for selects/autocomplete/etc widgets in an exposed filter?

Its in the filter handler when the fields are defined in views?

I could have a go at looking at this. What section of PIFR deals with this?

The views should be defined somewhere in the pifr_server component ... I'm guessing it's in /server/views.

I just implemented the exposed filters using the views gui, so a patch which adds them to the default views would also be a bonus.