MySQL Bugs: #69569: make the "affects me" count visible to everyone

Bug #69569	make the "affects me" count visible to everyone
Submitted:	25 Jun 2013 9:03	Modified:	27 Dec 2013 15:13
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Websites: bugs.mysql.com	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
To make this new communication feature even more two-way: communicate back the total number of affected users to all users

How to repeat:
Check existing bug reports: "affects me" only communicates back whether the current user has set the "affects me" option, but not how many users in total have ...

Suggested fix:
Make it more similar to how the PHP bugs system on bugs.php.net (the mother of bugs.mysql.com) does it. There number of votes (and average etc. which don't apply here as there is only a simple black/white "affects me") are public:

e.g. on https://bugs.php.net/bug.php?id=65112

Votes:	1
Avg. Score:	5.0 ± 0.0
Reproduced:	1 of 1 (100.0%)
Same Version:	1 (100.0%)
Same OS:	0 (0.0%)

Thank you for the feature request!

Thanks,
Umesh

Where is this subscribe counter? I don't see it, see screenshot I see for example of this bug.

I don't see any subscribe counters. If they are somewhere else please show me where they are.

Attachment: Screen Shot 2013-12-27 at 17.03.55.png (image/png, text), 48.28 KiB.

Hi Simon,
My Mistake - There is no visible counter. 
My Previous comment removed and revised here) should read:
  Thanks for the suggestion. 
  Please note that 'Affects Me' is intended to provide us feedback on the 
  'individual impact' of bugs on users. It is not intended as a general 'voting 
  mechanism'.

Sorry for the confusion

Fair enough. There's already a Email Updates button which interested parties might use to keep up to date and the affects me might give you a bit more feedback which is why it's interesting to more parties.

It is unfortunate that you do not want to share this information with the community as I think it would be useful. I do not really see the harm in making this information public and it is clear from your own comments that Oracle does use this information internally.