You are right, it looks a little strange, but this is more an usability issue than a bug.

1) Depending on your configuration, if you allow people to change their username (which is by default the email, when you don't ask for username at registration), then username might become different from email.

Also the same form allows to do it in 2 steps: first get username, then use username to reset password.

2) I'm a little reluctant to change this 2-steps process into 1-step process, as it would make changing someone's else password to easy (of course the new password wouldn't be known from the joker, but it would be an annoyance to the user).

We are planing to improve the workflow in CB 1.3.

I also sent you an email.