ID regeneration and system locks
Has anyone else noticed that not only does changing a set key and/or regenerating item IDs not generate any logs at all (no version or activity)? but also, it doesn't matter whether items have a system or manual lock, when an admin selects regenerate item IDs all items in the set (locked or not) get a new ID.
The only way to trace the change of IDs is IF a baseline was created between the changes, but the single item version doesn't show the change of the IDs. If no baseline is created or multiple regenerations occur in between baselines, it's impossible to track what happened to IDs or who changed them.
Even if only project/org admins can regenerate IDs, it's still very concerning, as the locks should be stopping this type of action, and a version change should be triggered. I even checked the database and there is no way to trace who makes these changes.
I sent a ticket to Jama support, but figured I would share with the community, as this is a big problem for configuration control in the industries we work for.