No my comment wasn't about the component field of Jira it was about where to put validation logic in an application.
There is a very valid use case to put it on the boundary of the system. For example when data enters the system you probably want to validate it. This might be done through bean validation (Spring MVC has support for it https://spring.io/guides/gs/validating-form-input/) or as part of the implementation of an aggregate root as you stated yourself.
But I don't think validating an object when persisting it in the database makes any sense in a well structured application.
If it doesn't match the constraints encoded in the database this is a bug and not a case for validation.
If it is invalid according to your business rules it shouldn't have been created in the first place.