Exactly. Fixing bugs is one of the best ways to learn a new codebase. Assuming you have a process for code reviews and some form of testing in place, it's not like there's much risk of a bad change getting out.

I'd actually lean the other way: No one should be adding new features to an existing codebase without having successfully done some fixes first.