### Deprecation Summary This issue is the deprecation issue for the GitLab Credits usage GraphQL fields removed in 20.0. It started with `eventType` (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/266591) and now also covers the 22 per-wallet and metadata fields deprecated by https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872. One announcement entry, `data/deprecations/19-6-graphql-gitlab-credits-usage-fields.yml`, covers all of them, and the *Removal plan (20.0)* section below lists every field and the code that goes with it. #### `eventType` The `eventType` field on the `GitlabSubscriptionUsageUserEvent` GraphQL type (`subscriptionUsage.usersUsage.users.events.nodes.eventType`) is deprecated in favour of `flowType`. `eventType` carries the raw usage-event source (`ai_token_usage`, `workflow_execution`, …), which identifies the billing pipeline an event came through, not what the user did. `flowType` carries the user-facing flow name (Agentic Chat, Code Review Flow, …) that the GitLab Credits dashboard has displayed since 18.7 (https://gitlab.com/gitlab-org/gitlab/-/work_items/581215). The field is already `null` whenever `events` is queried with `includeNonBillable: true`. [GraphQL reference: GitlabSubscriptionUsageUserEvent](https://docs.gitlab.com/api/graphql/reference/#gitlabsubscriptionusageuserevent) #### Per-wallet and metadata fields The usage billing dashboard that read the per-wallet breakdown and the subscription metadata was deleted in https://gitlab.com/gitlab-org/gitlab/-/commit/c79d0a39455a. The GitLab Credits dashboard that replaced it reports usage for the subscription as a whole. Nothing in GitLab reads these fields anymore, and several cost a CustomersDot request each to resolve (`paidTierTrial`, `monthlyWaiver`, `overage`, `monthlyCommitment`). `subscriptionUsage` and `currentUser.creditsUsage` are `experiment` fields, so removing them outright would be allowed; we deprecate and announce instead so API users get the standard window. | Type | Deprecated fields | Reason | |---|---|---| | `GitlabSubscriptionUsage` | `monthlyWaiver`, `monthlyCommitment`, `overage`, `paidTierTrial` | Usage is no longer broken down by wallet. Use `creditsUsed` and `dailyUsage` | | `GitlabSubscriptionUsage` | `lastEventTransactionAt`, `purchaseCreditsPath`, `subscriptionPortalUsageDashboardUrl`, `overageTermsAccepted`, `canAcceptOverageTerms`, `dapPromoEnabled` | No longer used by GitLab and will be removed without replacement | | `GitlabSubscriptionUsageUsersUsage` | `creditsUsed`, `dailyUsage` | Use the same field on `GitlabSubscriptionUsage` | | `GitlabSubscriptionUsageUsersUsage` | `totalUsersUsingCredits`, `totalUsersUsingMonthlyCommitment`, `totalUsersUsingOverage` | No longer used by GitLab and will be removed without replacement | | `GitlabSubscriptionUsageUserUsage` | `creditsUsed`, `monthlyCommitmentCreditsUsed`, `monthlyWaiverCreditsUsed`, `overageCreditsUsed`, `paidTierTrialCreditsUsed` | Usage is no longer broken down by wallet. Use `totalCreditsUsed` | | `GitlabSubscriptionUsageUserUsage` | `totalCredits` | No longer used by GitLab and will be removed without replacement | | `GitlabSubscriptionUserCreditsUsage` | `usedFlowTypes` | No longer used by GitLab and will be removed without replacement | #### Migration guidelines Select `flowType` instead of `eventType` on `GitlabSubscriptionUsageUserEvent`. For the subscription total use `creditsUsed` and `dailyUsage` on `GitlabSubscriptionUsage`; for a user's total use `totalCreditsUsed` on `GitlabSubscriptionUsageUserUsage`. The remaining fields have no replacement. No automated migration; the GitLab frontend does not read `eventType` (verified: no reference under `ee/app/assets/javascripts/usage_quotas` or its Jest specs; the events query selects `flowType` only). #### Background The field mirrors the CustomersDot field `GitlabCreditsEvent.eventType`, which CustomersDot deprecated for the same reason ("Use flow_type instead"). GitLab is its last consumer: `Gitlab::SubscriptionPortal::SubscriptionUsageClient::GET_USER_EVENTS_QUERY` selects it only to populate this field. Deprecating and then removing the GitLab field lets the client stop selecting it, which in turn lets CustomersDot remove its deprecated field. Removal chain: 1. ✅ GitLab 19.6: `GitlabSubscriptionUsageUserEvent.eventType` marked deprecated — https://gitlab.com/gitlab-org/gitlab/-/merge_requests/266591 (merged 2026-11-03). 1. GitLab 19.6: the 22 per-wallet and metadata fields marked deprecated — https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872 (in review). 1. GitLab 20.0: remove every field in *Removal plan (20.0)* below, including dropping `eventType` from `GET_USER_EVENTS_QUERY`. 1. CustomersDot: remove `Types::Subscriptions::GitlabCredits::UsersUsage::EventType#event_type` once no supported GitLab version selects it. #### Usage history (from `git log -S'eventType'` on `ee/app/assets/javascripts/usage_quotas`) | Date | GitLab | Change | Reference | |---|---|---|---| | 2025-09-17 | 18.5 | Events table added to the user dashboard; the **Action** column rendered `eventType` | `a31d64c7075d`, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/205107 | | 2025-12-05 | — | CustomersDot adds `flowType` to `GitlabCreditsEvent` and deprecates `eventType` ("Use flow_type instead") | CustomersDot `c6aad911a4`, https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/14228 | | 2025-12-09 | 18.7 | Action column switched to `flowType`; `eventType` kept only as a fallback (`item.flowType \|\| item.eventType`) | `5681f2c1cb45`, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/215289 | | 2026-10-29 | 19.6 | Fallback and the `eventType` selection removed from the frontend events query — last frontend reader gone | `23fbeef53785`, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/265821 | `eventType` was the displayed value for two milestones (18.5–18.6), a fallback for ten months, and has had no reader in GitLab since https://gitlab.com/gitlab-org/gitlab/-/merge_requests/265821. The GraphQL field has been populated from CustomersDot the whole time and remains so until the 20.0 removal. ### Breaking Change? Does this deprecation contain a breaking change? ```Yes``` — removing the fields at 20.0 breaks any GraphQL client still selecting them. They are behind `authorize :read_subscription_usage` / `authorize :read_user` on the GitLab Credits dashboard data; the GitLab UI does not use them. ### Affected Customers Who is affected by this deprecation: - [x] GitLab.com - [x] Self-managed - [x] Dedicated What pricing tiers are impacted? - [ ] GitLab Free - [x] GitLab Premium - [x] GitLab Ultimate ### Deprecation Milestone This deprecation is being announced in milestone: ```19.6``` ### Planned Removal Milestone The feature / functionality will be removed in milestone: ```20.0``` #### Rollout Plan - DRI Engineers: `@sheldonled` - DRI Engineering Manager: `@aish.sub` - [ ] No feature flag: a schema deprecation takes effect on deploy. Before 20.0, check field usage in Kibana per https://docs.gitlab.com/development/graphql_guide/monitoring/#see-field-usage. - [x] 20.0 removal plan: folded into this issue (*Removal plan (20.0)* below); https://gitlab.com/gitlab-org/gitlab/-/work_items/637339 closed as a duplicate. #### Communication Plan - DRI Product Manager: `@brothwell1` **Internal Communication Plan** - [ ] Breaking change request filed (https://gitlab.com/gitlab-com/Product/-/issues/new?description_template=Breaking-Change-Exception) — needed for the 20.0 removal - [ ] Support Preparedness issue created - [ ] Guidance for Engineering, Product, Security, Customer Success, and Sales created **External Communication Plan** - [ ] Customer announcement plan - [ ] Deprecation announcement entry in `data/deprecations/` so it appears in release posts and https://docs.gitlab.com/update/deprecations/ (`19-6-graphql-gitlab-credits-usage-fields.yml`, in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872) - [x] Documentation updated (GraphQL reference is regenerated from the schema by the deprecation MRs; `eventType` shipped in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/266591, the rest ships in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872) - [ ] On the major milestone: - [ ] The deprecated item has been removed. - [ ] The removal MR is labeled ~"breaking change". #### Removal plan (20.0) Removal of a deprecated GraphQL field is a ~"breaking change" and happens on the major milestone. This plan covers `eventType` and the 22 GitLab Credits usage fields deprecated in 19.6 by https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872 (deprecation issue https://gitlab.com/gitlab-org/gitlab/-/work_items/637315): all share the removal milestone, the cause (the usage billing dashboard that read them was deleted in https://gitlab.com/gitlab-org/gitlab/-/commit/c79d0a39455a) and the announcement entry `data/deprecations/19-6-graphql-gitlab-credits-usage-fields.yml`. The removal MR needs the ~"breaking change" label and `Changelog: removed`. **Fields to remove** | Type | Fields | |---|---| | `GitlabSubscriptionUsageUserEvent` | `eventType` (replacement: `flowType`) | | `GitlabSubscriptionUsage` | `monthlyWaiver`, `monthlyCommitment`, `overage`, `paidTierTrial`, `lastEventTransactionAt`, `purchaseCreditsPath`, `subscriptionPortalUsageDashboardUrl`, `overageTermsAccepted`, `canAcceptOverageTerms`, `dapPromoEnabled` | | `GitlabSubscriptionUsageUsersUsage` | `totalUsersUsingCredits`, `totalUsersUsingMonthlyCommitment`, `totalUsersUsingOverage`, `creditsUsed`, `dailyUsage` | | `GitlabSubscriptionUsageUserUsage` | `creditsUsed`, `totalCredits`, `monthlyCommitmentCreditsUsed`, `monthlyWaiverCreditsUsed`, `overageCreditsUsed`, `paidTierTrialCreditsUsed` | | `GitlabSubscriptionUserCreditsUsage` | `usedFlowTypes` | Not in scope (kept deliberately as API capabilities): `users(searchQuery:)`, `dailyUsage(sort:, limit:)`, `events(includeNonBillable:)`, `usedFlowTypes(includeNonBillable:)`, `GitlabSubscriptionUsageUserEvent.locationId`. **Before removing** - [ ] Check production usage of each field in Kibana per https://docs.gitlab.com/development/graphql_guide/monitoring/#see-field-usage. Note the result here. - [ ] Confirm the deprecation announcement entry `data/deprecations/19-6-graphql-gitlab-credits-usage-fields.yml` shipped with https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872. **Changes: GraphQL types** 1. `ee/app/graphql/types/gitlab_subscriptions/subscription_usage/event_type.rb`: remove `event_type`. 1. `ee/app/graphql/types/gitlab_subscriptions/subscription_usage/user_type.rb`: remove `event_type` from the `UserEvent` struct and from `load_users_events` (`event_type: event[:eventType]`); drop the "`eventType` is null" clause from the `includeNonBillable` argument description. 1. `ee/app/graphql/types/gitlab_subscriptions/subscription_usage_type.rb`: remove the ten fields above. 1. `ee/app/graphql/types/gitlab_subscriptions/subscription_usage/users_usage_type.rb`: remove the five fields above. 1. `ee/app/graphql/types/gitlab_subscriptions/subscription_usage/user_usage_type.rb`: remove the six fields above, leaving `totalCreditsUsed` and `nonBillableCreditsUsed`. 1. `ee/app/graphql/types/gitlab_subscriptions/user/credits_usage_type.rb`: remove `used_flow_types`. 1. Delete the types that are then unreferenced: `MonthlyWaiverType`, `MonthlyCommitmentType`, `OverageType`, `PaidTierTrialType` (all under `subscription_usage/`). **Changes: lib and client** 1. `ee/lib/gitlab_subscriptions/subscription_usage.rb`: remove `monthly_waiver`, `monthly_commitment`, `overage`, `paid_tier_trial`, `last_event_transaction_at`, `purchase_credits_path`, `overage_terms_accepted`, `can_accept_overage_terms`, `dap_promo_enabled`, `usage_dashboard_path`, `subscription_portal_usage_dashboard_url`, and the `MonthlyWaiver`, `MonthlyCommitment`, `Overage`, `PaidTierTrial` structs. 1. `ee/lib/gitlab_subscriptions/subscriptions_usage/user_usage.rb`: remove `daily_usage`, `total_users_using_credits`, `total_users_using_monthly_commitment`, `total_users_using_overage`, `credits_used`. 1. `ee/lib/gitlab_subscriptions/subscriptions_usage/user/credits_usage.rb`: remove `used_flow_types`. 1. `ee/app/models/gitlab_subscriptions/subscriptions_usage/user_consumption_statistics.rb`: remove `total_credits`, `credits_used`, `monthly_commitment_credits_used`, `monthly_waiver_credits_used`, `overage_credits_used`, `paid_tier_trial_credits_used`. 1. `ee/lib/gitlab/subscription_portal/subscription_usage_client.rb`: - delete `GET_PAID_TIER_TRIAL_QUERY`, `GET_MONTHLY_WAIVER_QUERY`, `GET_OVERAGE_QUERY` and `get_paid_tier_trial`, `get_monthly_waiver`, `get_overage`; - keep `get_monthly_commitment` and `GET_MONTHLY_COMMITMENT_QUERY`: `GitlabSubscriptions::FetchMonthlyCommitmentService` uses them for the billing pages; - trim `GET_METADATA_QUERY` to `startDate`, `endDate`, `enabled`, `isOutdatedClient`; - trim `GET_USERS_USAGE_STATS_QUERY` to `totalActiveUsers`; - trim `GET_USERS_USAGE_QUERY` and `GET_CONSUMERS_QUERY` to `userId`, `totalCreditsUsed`, `nonBillableCreditsUsed` (plus `entityType` for consumers); - drop `eventType` from `GET_USER_EVENTS_QUERY`. `GET_USER_EVENTS_WITH_NON_BILLABLE_QUERY` already omits it; once both queries select the same event fields, consider whether the two still need to differ beyond the `includeNonBillable: true` argument; - keep `get_used_flow_types_for_user_id`: `GitlabSubscriptionUsageUser.usedFlowTypes` (the per-user drill-down filter) still uses it. **Changes: specs, docs, announcement** 1. Type specs under `ee/spec/graphql/types/gitlab_subscriptions/` (field lists and the deprecation examples added by the deprecation MRs), `ee/spec/requests/api/graphql/gitlab_subscriptions/subscription_usage_spec.rb`, `ee/spec/requests/api/graphql/gitlab_subscriptions/user/credits_usage_spec.rb`, `ee/spec/lib/gitlab_subscriptions/subscription_usage_spec.rb`, `ee/spec/lib/gitlab_subscriptions/subscriptions_usage/user_usage_spec.rb`, `ee/spec/lib/gitlab/subscription_portal/subscription_usage_client_spec.rb` and the fixtures that carry the removed fields. 1. Regenerate docs and schema: `bin/rake gitlab:graphql:update_all`. 1. Add the removal to `data/removals/` (or the current removals location) so it appears in https://docs.gitlab.com/update/deprecations/, and list the fields in `doc/api/graphql/removed_items.md`. **Follow-up (CustomersDot)** Once no [supported GitLab version](https://docs.gitlab.com/policy/maintenance/) selects them, open a CustomersDot issue to remove the matching fields from `Types::Subscriptions::GitlabCredits`: `UsersUsage::EventType#event_type` (`app/graphql/types/subscriptions/gitlab_credits/users_usage/event_type.rb`, `deprecation_reason: 'Use flow_type instead'` since https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/14228), and whichever of the wallet-breakdown and metadata fields GitLab was the last consumer of. #### Labels - [x] This issue is labeled ~deprecation, and with the relevant `~devops::`, `~group::`, and `~Category:` labels. - [x] This issue is labeled ~"breaking change" because the 20.0 removal is a breaking change. Related: https://gitlab.com/gitlab-org/gitlab/-/work_items/637315 (the umbrella cleanup issue: CustomersDot client fallbacks, dead frontend surface, and the deprecation MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/267872).