Bug 760338 - Think about submission filtering -- do we need to, how might we?
Summary: Think about submission filtering -- do we need to, how might we?
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: cumin
Version: Development
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 2.3
: ---
Assignee: Trevor McKay
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 21:22 UTC by Trevor McKay
Modified: 2013-01-04 15:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-04 14:49:32 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.