If we assume a user has an entity relationship of a Parent/Child association and the user modifies just the child entity type, Envers will not specifically generate an audit row for the parent.
There are use cases where users would like to be able to specifically track some parent association when child entity types are modified. Presently this is only reasonably possible by having the user modify some attribute on the parent type so it gets included in the audit tracking.
Ideally we'd like to look into support where a user can trigger this behavior via some type of configuration through an annotation rather than explicit in their user code.
We may investigate this as part of HHH-11326.
A commit was mistakenly committed with a commit message that referred to this jira. It should have referred to HHH-12150:
Is this issue also related to ?
It is definitely similar; however, I'm not sure I necessarily want to enforce this behavior solely around the use of a @Version annotated attribute; however, we can definitely see.