Search
Closed
as Fixed Help for as Fixed

2
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 503165
Opened: 10/25/2009 3:24:47 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
See this:

https://connect.microsoft.com/securityessentials/feedback/ViewFeedback.aspx?FeedbackID=502806

That is marked as "private" yet, I was able to vote, and mark as reproduced. There are others that are similar.

I was not able to verify this same behavior on any other Connect beta site that I was capable of entering

NOTE: DO NOT CONFUSE this Connect beta site with the *newer* Microsoft Security Essentials "Ongoing" beta site!
Details (expand)
Product Version
Production Release
Reproduction Steps
1. Go to the Microsoft Security Essentials beta site, and enter the URL as mentioned above.
You will see it it marked as "Private"
2. vote and/or mark as reproducible
Expected Results
I would *not* expect to be able to access *any* item that is marked as "private"
File Attachments
0 attachments
Sign in to post a comment.
Posted by Don Carlson on 10/25/2009 at 3:57 PM
I was able to reproduce these results also. I had the ability to view, vote and submit to this "bug". Since I saw this problem with this "bug" I went over to another beta that I was participating in and changed one of my "active" bugs to "private". From there I sent the link to fellow beta testers and asked them if they could see this bug that I had changed to "private" and replied that they could not see this bug. They only received a message that stated "page not found". There seems to be a problem that needs to be corrected, private is private between the beta tester and Microsoft.
Posted by Microsoft on 10/26/2009 at 10:52 AM
Hi Dremt,

Thanks for letting us know this. We have contacted the administrator for that connection and fixed the problem.

Regards,
Roberto

Posted by Dremt on 10/26/2009 at 11:31 AM
Thanks Roberto,

I had also filed this on that MSE beta site in the hopes somewhere between your team and theirs, it would be fixed :)

Bob
Posted by Microsoft on 10/26/2009 at 3:27 PM
Hi Dremt,

Thanks for letting us know this. We have contacted the administrator for that connection and fixed the problem.

Regards,
Roberto