This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 220293 - Add dashboard table focused on members reporting
Summary: Add dashboard table focused on members reporting
Status: VERIFIED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Dashboard (show other bugs)
Version: 7.3
Hardware: PC Linux
: P2 normal (vote)
Assignee: Vladimir Riha
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-17 15:08 UTC by Jiri Kovalsky
Modified: 2012-10-23 09:25 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2012-10-17 15:08:17 UTC
Right now the overall table with bug counts on the team specific page contain also bugs reported by other teams. It would be great if the table only shows bug counts relevant for the team you are seeing.

http://quality2.netbeans.org/dashboard/web/view.php?id=7&version=7.3
Comment 1 Vladimir Riha 2012-10-17 17:27:05 UTC
I'm sorry but I don't think this is a good idea. The dashboard table on team's page is supposed to show issues in areas/components that the team covers. It doesn't show issues reported by team but more like TO (against) team.

If I limit it to the people instead, e.g. Web Tier team would not see many issues reported by e.g. NetCAT, QA, community etc. Bug limits would also make no sense then because not all bugs would be accounted. Minor conflict would be how to  resolve situation when a developer changes team.
Comment 2 Jiri Kovalsky 2012-10-18 10:12:33 UTC
Then we obviously have two perspectives at teams. Components based view and members based view which is in my opinion also valid. For the latter it of course makes no sense to show bug limits. The goal of this issue was to suggest that a member based table would be useful too as the assignment of components to testing teams is sometimes questionable.

Since this RFE is closed as WONTFIX I will continue manually querying Bugzilla and processing the result in a spreadsheet as in the past.
Comment 3 Vladimir Riha 2012-10-18 10:35:09 UTC
OK, so the current table stays as it is and I'll create a new one called like "Issues reported by team members" that:

- contains all areas as defined for given version
- contains exactly the same columns
- all bugs will be taken into account only if bug's reporter is a member of the team

This table would be visible only if team is focused on REPORTING. What do you think?
Comment 4 Jiri Kovalsky 2012-10-18 10:40:41 UTC
Yes, that would be perfect! Thanks Lado!
Comment 5 Vladimir Riha 2012-10-21 11:45:10 UTC
Implemented only for NetCAT team, link is 

http://quality2.netbeans.org/dashboard/web/netcat.php

The question would be where to put a link to this page. All team pages (view.php) share same template so it would either affect all pages or it would require some not so nice condition. Easy part would be to put it in Notes section in index page.

Please note that since NetCAT team is team like any other, there is not property like "isNetCAT". Therefore the netcat.php finds first team with name "NetCAT*"
Comment 6 Jiri Kovalsky 2012-10-22 09:06:58 UTC
For some reason P3 total bug count link redirects to netbeans.org homepage instead of displaying all the 477 P3 issues. Is it caused by too long URL?
Comment 7 Vladimir Riha 2012-10-22 09:09:09 UTC
Yes, sorry for that (the same happens with all too long links to bugzilla). I haven't found a time to fix it yet (probably later this week)
Comment 8 Jiri Kovalsky 2012-10-22 09:09:47 UTC
I agree that the link should be added to the team with "NetCAT" in its name. No more complex heuristic is needed. :)
Comment 9 Vladimir Riha 2012-10-22 09:11:44 UTC
OK, will do that. Truth is the worst case scenario is one more link on team's page, not a big deal
Comment 10 Vladimir Riha 2012-10-22 14:33:22 UTC
fixed and will be propagated within next 50 minutes

I'll fix the issue with links tomorrow
Comment 11 Jiri Kovalsky 2012-10-23 08:40:18 UTC
Excellent. I see "More NetCAT statistics" on NetCAT 7.3 team page [1], the link to long bug lists is working but JavaFX row is still empty. Is that reported elsewhere or should this bug be reopened?

[1] http://quality2.netbeans.org/dashboard/web/view.php?id=19&version=7.3
Comment 12 Vladimir Riha 2012-10-23 09:25:33 UTC
It's not reported, but feel free to do it :) The problem is that no one from NetCAT reported against JavaFX. There are similar other cases when this could happen in dashboard-like tables (no components in area, no bugs in area, no bug in component if you're looking at particular area...). Right now I'm not sure how to fix it but I'll try to come up with at least partial solution