Comment 7 for bug 1051029

Regressions are often caused because users use new functionality. That we have 7 such bugs in the regression listing right now. All regressions are ultimately caused by new features or bug fixes that step on other rules.

Consider that I set this condition up by approving a public blueprint for a sprint. It broke when "another" party set the blueprint to private. The other party can still see the listing and is not aware that the sprint organisers and attendee's cannot see the listing.