<!-- Implementation issues are used break-up a large piece of work into small, discrete tasks that can move independently through the build workflow steps. They're typically used to populate a Feature Epic. Once created, an implementation issue is usually refined in order to populate and review the implementation plan and weight. Example workflow: https://about.gitlab.com/handbook/engineering/development/threat-management/planning/diagram.html#plan --> ## Why are we doing this work As part of a [spike issue](https://gitlab.com/gitlab-org/gitlab/-/issues/225590#note_407113917), it surfaced that certain fields in `Vulnerability` are always null. We'd like to remove them to simplify the DB and rails model. ## Relevant links Fields in `Vulnerability` that are always NULL: - [x] `milestone_id` - https://explain.depesz.com/s/59td ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136656), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138262)) - [x] `epic_id` - https://explain.depesz.com/s/e2FG ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136662), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138263)) - [x] `updated_by_id` - https://explain.depesz.com/s/hYHj ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136663), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138264)) - [x] `last_edited_by_id` - https://explain.depesz.com/s/hYHj ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136664), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138266)) - [x] `start_date` - https://explain.depesz.com/s/hYHj ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136665), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138268)) - [x] `due_date` - https://explain.depesz.com/s/hYHj ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136666), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138267)) - [x] `last_edited_at` - https://explain.depesz.com/s/hYHj ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136667), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138269)) - [x] `start_date_sourcing_milestone_id` - https://explain.depesz.com/s/gbWY ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136668), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138270)) - [x] `due_date_sourcing_milestone_id` - https://explain.depesz.com/s/gbWY ([ignore MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136669), [drop MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138271)) ## Implementation plan <!-- Steps and the parts of the code that will need to get updated. The plan can also call-out responsibilities for other team members or teams. --> - [x] Prepare MRs for the [3-milestone process](https://docs.gitlab.com/ee/development/database/avoiding_downtime_in_migrations.html#dropping-columns) <!-- Workflow and other relevant labels ~"group::" ~"Category:" ~"GitLab Ultimate" -->