Repository navigation
PM-6740: Filter customer revenue by offering type - #2613
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Revenue offering type selector to the Customer section for PM-6740. Users can select AI Training, Crowd Powered Outcomes, Crowd Powered Innovation, Flexible Talent, TopGear, or TaaS Ops and combine that selection with Revenue account category to see matching customers and recognized revenue.
Uses the API's offering-scoped customer matrices, including the existing blank-offering corrections and TopGear Ops mapping. Filters update Revenue Customer-Wise without new requests or changes to revenue charts or Goods Sold. ALL restores the full dataset. Monthly/quarterly totals and selections survive refresh; missing and empty source data have explicit states. The shared dashboard component exposes the control in both Sales and Reports.
Requires reports-api-v6 #211; deploy the API first.
Validation: 68 focused dashboard tests passed, including combined filters, customer totals, quarterly totals, refresh persistence, unchanged goods sold, and missing/empty selections. ESLint on changed TypeScript files and the full TypeScript check (
tsc --noEmit) passed after syncing the existing lockfile dependencies.