Hello, I was assigned to design the search/filter component for the applications list and would like to bring some questions. I already got some requirements from Liz/Thomas. My proposal would be to present a behaviour similar to what JIRA does. They have “dropdown” selectors to allow filtering + a search box (initially). For our context, the dropdowns would be to filter State (Up, Down etc.) and Type (EAP, Wildfly etc.). We probably don’t need the find input in the beginning, when we have not many options. Thomas brought this comment: > The input text should still be editable to do more filtering such as: > "(status=DOWN OR status=UNKNOWN) AND hostname ~ 'corp.redhat.com > <http://corp.redhat.com/>' " (To show all servers on *.corp.redhat.com > <http://corp.redhat.com/> that are down or unknown) JIRA also covers that, when clicking on Advanced, the dropdowns are hidden and everything goes inside the search input: I like this approach because we offer something user-friendly and at the same time provide something more powerful for advanced users. I would like to hear your feedback. @Inventory team, from what was presented, it is feasible to be implemented? Thanks, Gabriel Gabriel Cardoso UX designer @ Red Hat

On Jun 30, 2015, at 6:35 PM, Thomas Heute <theute(a)redhat.com&gt; wrote: For now we are looking for relatively simple filtering (rather than search). On the app server list, I guess we would want to filter on status AND hostname. For instance, I may want to filter the whole list for all servers on *.corp.redhat.com that are DOWN OR UNKNOWN If we allow for a user "query language" should be easy to understand by non hardcore developers, like in JIRA. Thomas On 06/30/2015 05:43 PM, Lukas Krejci wrote: > What kind of query language are we going to support here? How will it > represent (if at all) the graph nature of inventory entities (e.g. gimme all > resources of type EAP in the "test" environment which relate to data source DS > by relationship "uses")? > > On Tuesday, June 30, 2015 16:34:55 Gabriel Cardoso wrote: >> Hello, >> >> I was assigned to design the search/filter component for the applications >> list and would like to bring some questions. I already got some >> requirements from Liz/Thomas. >> >> My proposal would be to present a behaviour similar to what JIRA does. They >> have “dropdown” selectors to allow filtering + a search box (initially). >> >> >> >> For our context, the dropdowns would be to filter State (Up, Down etc.) and >> Type (EAP, Wildfly etc.). We probably don’t need the find input in the >> beginning, when we have not many options. >> Thomas brought this comment: >>> The input text should still be editable to do more filtering such as: >>> "(status=DOWN OR status=UNKNOWN) AND hostname ~ 'corp.redhat.com >>> <http://corp.redhat.com/>' " (To show all servers on *.corp.redhat.com >>> <http://corp.redhat.com/> that are down or unknown) >> JIRA also covers that, when clicking on Advanced, the dropdowns are hidden >> and everything goes inside the search input: >> >> >> >> I like this approach because we offer something user-friendly and at the >> same time provide something more powerful for advanced users. >> >> I would like to hear your feedback. >> @Inventory team, from what was presented, it is feasible to be implemented? >> >> Thanks, >> Gabriel >> >> Gabriel Cardoso >> UX designer @ Red Hat > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev