SirSebstar wrote:no function that allows you to create br's on your own would not consitute not a bug.or in clearer english
it was tested that the functionality would not screw up the cc database. The unexpected functionality of making br's is a bug.
this is a bug, the fact that you can make it do something that was OBVIOUSLY not intended is not a functionality. please use a bit of common sense.
Can we get a link to the announcement where the intended purpose of this functionality is??? With any development project now days, I would assume all requirements are clearly defined, coded to, and tested against. Perhaps a member can be added to the Beta testers that types up the new func details and they are announced to the public prior to go-live instead of getting these surprises.
IMO, exploiting all the bugs is the best way to get these development cycles. Another member should be added to the Beta testers to test out the user experience of said features.
It's 2013, development cycles (requirements > dev > unit > functional > user testing > go-live) is not a new concept anymore.
Not trying to be a jerk, just trying to fix this from happening with every [unexpected] release. At least tell us "We are going live Saturday with a new blah blah blah feature". So we aren't surprised saturday when everything is different when we log in, we can get used to the upcoming concepts before having them thrown at us. Just my two cents.