Sounds like a bug.
One thing to check - make sure the new field is also added to the Undefined requirement type. I know not having a requirement field visible for that type could cause some strange behavior in previous versions.
Sounds like a bug.
One thing to check - make sure the new field is also added to the Undefined requirement type. I know not having a requirement field visible for that type could cause some strange behavior in previous versions.