Skip to content

Draft: [DO NOT MERGE] Add epics.issue_id NOT NULL constraint

Alexandru Croitor requested to merge add_not_null_constraint_to_epics_issue_id into master

What does this MR do and why?

This MR adds a not-null constraint to the issue_id column of the epics table. This will prevent any epics from being created without an issue ID.

We are also removing the sync_epic_to_work_item FF as we can no longer disable the FF once the NOT NULL constraint on epics.issue_id column is introduced. Disabling the FF would mean avoiding creation of epic work item for a given legacy epic, which would result in violating the NOT NULL constraint on `epics.issue_id` column.

NOTE: This MR cannot be merged before we have epic sync FFs set to on by default.

re #450976

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

Edited by Alexandru Croitor

Merge request reports