Bug 1162436

Summary:	[RFE][horizon]: [data processing] Add filtering to tables
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aortega, athomas, lbopf, markmc, mrunge, nbarcet, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/data-processing-table-filtering
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	python-django-horizon-2015.1.0-9.el7ost	Doc Type:	Enhancement
Doc Text:	The results displayed in tables for the Data Processing service can now be filtered to allow the user to see only those results that are relevant.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:15:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-11-11 05:06:26 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/data-processing-table-filtering.

Description:

In the data processing panels, there are several tables that can become rather lengthy.  Given that, it is desireable to incorporate filtering.

As discussed at the Kilo summit, tables that need filtering applied:
Node group templates (by plugin)
Cluster templates (by plugin)
Job execution (by cluster)
Jobs (by job type?)

The target date for this is early in the Kilo cycle.

Specification URL (additional information):

None

Comment 6 errata-xmlrpc 2015-08-05 13:15:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548