[
https://issues.jenkins-ci.org/browse/JENKINS-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161948#comment-161948
]
dogfood commented on JENKINS-12984:
-----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_analysis-core
#10440|http://ci.jenkins-ci.org/job/plugins_analysis-core/10440/]
[FIXED JENKINS-12984] Added option to filter the projects in the table.
(Revision 6ce8685a33cbeab5eac2ac9cc0b3b04a8dfb8bc7)
Result = SUCCESS
Ulli Hafner :
Files :
*
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config.jelly
*
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/portlet.jelly
*
src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet.java
*
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config_de.properties
> 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
