-
Improvement
-
Resolution: Unresolved
-
Major
-
None
I know there is a drop down plugin. that is not what I am looking for, as it, in my opinion, it decreases visibility
What I think would be better is to have either one of
A. jenkins configuration, # of dashboard rows, views are split either alphabetically, and based on string length of names across available rows [crude but simple?]
B. per view configuration, indicate what row # the view should be on [possibly more complex, but more elegant?]
CONOPS. large code base, multiple branches, multiple developers, multiple features
with ~30 views in the dashboard in one row its unwieldy. 10 views per row over 3 row (maybe an extra row for default 'all' view might work much better in this scenario....
e.g.
have one row with all feature filtered jobs
have one row with all branch filtered jobs
have one row with all developer filtered jobs
this way feature lead can oversee changes regardless of branch/developer who touched
this way branch/release lead can oversee all changes regardless of developer/feature impacted
this way developer can oversee all changes regardless of thread/feature