I flagged this bug in the email I sent to @cpennington @markchang and you on Friday. I called it inconsequential, but perhaps you disagree. The behavior is that if you hit the "unset" or whatever it's called button, the values stay the same but show as not explicitly set. I don't recall how it behaves on reload. I don't think it's a bug I caused. The reason it didn't occur before was that we were always explicitly setting all the fields via the templates.