Comment 7 for bug 1794588

No, sorry about the confusion. bug 1040686 was the xul-era bug that was filed to report problems with the previous behavior in xul. This is the same behavior that your bug is seeking to restore. We set that bug to "Won't Fix" because the behavior is different in the web client.

What I'm trying to say is that people want the updating of call numbers to work differently depending on the particular use case. This is why I'm suggesting that we find a way to accommodate both behaviors, or to have the client behave differently when the copy(ies) being edited is the last copy belonging to the call number. It seems as if this isn't a one size fits all situation.