Acceptance Criteria
- Create storage layer for reading/writing event types from/to the database
This should be added on the EventStore
This should be added on the EventStore
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Change data storage layer to include 'event_types' field | mediawiki/extensions/CampaignEvents | master | +67 -14 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Daimona | T355253 [EPIC] Display data on event type | |||
| Resolved | MHorsey-WMF | T387487 Create storage layer for event type | |||
| Resolved | MHorsey-WMF | T387488 Update DB schema for storing event types | |||
| Declined | None | T387483 Drop DB schema that supports a single event type | |||
| Resolved | Marostegui | T394509 Drop unused event_type (varbinary) field and replace with event_types(integer) field in production |
Change #1144628 had a related patch set uploaded (by Mhorsey; author: Mhorsey):
[mediawiki/extensions/CampaignEvents@master] Change data storage layer to include 'event_types' field
Change #1144628 merged by jenkins-bot:
[mediawiki/extensions/CampaignEvents@master] Change data storage layer to include 'event_types' field
I am able to create, enable, edit and view events in prod and betacluster. Marking this as done.