[
https://issues.jenkins-ci.org/browse/JENKINS-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159867#comment-159867
]
Greg Moncreaff commented on JENKINS-12984:
------------------------------------------
An ALTERNATE, which has its own pros and cons, is to update the generic table
element to allow the viewer to filter/reduce by some control on the title bar
of each table. This could be used to affect other tabular reports (like
build/job statistics) to eliminate rows (or even columns) with no (meaningful?)
information.
Some sort of compression glyph "><" (gt;lt;) to indicate column minimization
(and glyph toggles to "<>" to show that it can be expanded?). "^/V" to
indicate row minimization, etc. This state is probably something that should
be "sticky".
> warnings (et.al) per project - add checkbox to filter out projects with issue
> total of 0? - or to show only the top N based on sort selection?
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-12984
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12984
> Project: Jenkins
> Issue Type: Improvement
> Components: warnings
> Affects Versions: current
> Reporter: Greg Moncreaff
> Assignee: Ulli Hafner
> Attachments: jenkins-table_per_project-information_reduction.bmp
>
>
> CONOPS - reduce information overload by allowing to focus on a subset when
> dashboard view contains many jobs
> Options
> 1. just filter out the zero issue projects
> = most likely they are fine and need no extra attention? possibly, but
> less likely? that there publishers are not working for some reason
> 2. put a cap on number of rows, so you can focus on the top (or bottom) N (3,
> 10) whatever based on the sort bring projects into/out of the the limited row
> set?
> for option 2, (and in general) you would want the sorts to be sticky, so
> whatever sort showed the current "interesting" job subset would remain until
> actively changed.
> either or both options could be done independent of each other
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
