Add not-null db constraint for requirement issue
As we now delegate attributes from requirement to requirement issue (so the issue is SSOT) and we validate that the issue is present, it would be good to have also DB constraint that requirement's issue_id can't be nil.
The following discussion from !74296 (merged) should be addressed:
-
@jprovaznik started a discussion: (+4 comments) not-blocking (could be a follow-up): should we remove
, allow_nil: true
now? I would expect that now it's required for a requirement to have an issue? @cablett WDYT? Maybe this was needed for DB migration phase only?