Rollout required `iid` field for AutoFlow-related Work Item Events

The AutoFlow workers introduced in AutoFlow: emit issue-related events (!177277 - merged) depend on the work item iid field. In order to not retrieve it for every event in the worker it should be a required field on the respective events.

Events affected:

• Work Item created
• Work Item updated
• Work Item closed
• Work Item reopened

The MR AutoFlow: emit issue-related events (!177277 - merged) will already introduce the iid field as an optional event field and the new AutoFlow workers will use it if available or else retrieve it from the database.

According to https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/event_store.md#add-properties two more rollout phases need to be addressed:

1. Rollout 1: done in AutoFlow: emit issue-related events (!177277 - merged)
   • Add new properties as optional (not required).
   • Update the subscriber so it can consume events with and without the new properties.
2. Rollout 2:
   • Change the publisher to provide the new property
3. Rollout 3: (if the property should be required):
   • Change the schema and the subscriber code to always expect it.

changed milestone to %17.10

added Category:AutoFlow featureaddition groupenvironments workflowready for development labels

added typefeature label

added devopsdeploy sectioncd labels

set weight to 1

mentioned in merge request !177277 (merged)

assigned to @timofurrer

The analytics instrumentation label is automatically applied when featureaddition and workflowready for development labels are applied. We encourage teams to plan for instrumentation at the time of feature development for new features. This label helps groupanalytics instrumentation to proactively reach out to teams that require instrumentation support. In case instrumentation does not apply to this feature, please feel free to remove the label.

added analytics instrumentation label

mentioned in issue gitlab-org/quality/triage-reports#21892 (closed)

closed