Not a bug, more a QoL settings.
Currently item damage can be set or globally from the globals.xml or per item in the cfgspawnabletypes.xml.
The latter is mostly used to define what spawns inside a container, so not all types are present there.
Adding the min/max damage [with -1 as default] would avoid having to define all the types that cannot be fixed [like glasses] in the spawnabletypes.
In the types.xml each entry has the cost value that I assume is deprecated because doing any changes to it breaks all types.

This instead might be a bug: having any type set with deloot=1 causes the item not to spawn anymore after a week or so, no matter if any other flag is set to 0 or 1. Currently the workaround is to add a custom usage in limitdefinition and adding that to both the type and the groupproto [FAL and SVD being the main examples]