Now that the dedicated requirement object `RequirementsManagement::Requirement` is only used for its IID we need to add support for a Requirement work item reference to be used as well. Once the IID has been deprecated and we've given customers using the existing IIDs time and tools to migrate over to Work Items, support for the old IID can be removed and those objects and table can be destroyed upon some major version. See https://gitlab.com/gitlab-org/gitlab/-/issues/329435#note_1165101278: * Add support for work item iid as well as an legacy requirement IID https://gitlab.com/gitlab-org/gitlab/-/issues/329435 in test cases * and anywhere else requirement IID is used. * Broadcast a deprecation of IID support and offer a migration for moving these somehow from IIDs to work item URLs for customers relying on it * or if not a migration, maybe a date after which this old format will no longer work so they can change their yml files, but the artefacts might just have to stay the old format? :grimacing: * After deprecation period is over (major version?) drop support for IIDs * Then we're clear to https://gitlab.com/gitlab-org/gitlab/-/issues/345308 and then https://gitlab.com/gitlab-org/gitlab/-/issues/329432 - Detailed strategy in https://gitlab.com/groups/gitlab-org/-/epics/9203#note_1173884563 - Broad deprecation comms strategy in https://gitlab.com/groups/gitlab-org/-/epics/9203#note_1180587324