Bug 760338

Summary:	Think about submission filtering -- do we need to, how might we?
Product:	Red Hat Enterprise MRG	Reporter:	Trevor McKay <tmckay>
Component:	cumin	Assignee:	Trevor McKay <tmckay>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	Development	CC:	croberts, matt, mkudlej
Target Milestone:	2.3
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-04 14:49:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Trevor McKay 2011-12-05 21:22:12 UTC

Description of problem:

Running with the job server enabled potentially gives us a huge number of submissions.  Cumin currently has a freshness filter for submission display, which is fixed in the code.

Should the filter be configurable?  Should we allow sorts/filters on screen by submission date?  Are there are useful subgroupings that users might want do on a big submission display (or maybe this is handled as part of a reporting suite?)

Think about this stuff.

Comment 1 Trevor McKay 2012-09-04 14:49:32 UTC

This was really meant as a tracker.  I'll close it and maintain it as a roadmap item until/unless we have specific changes in mind.