Conversation
What was broken The Reports Portal API returned only the original dashboards, so it could not supply monthly member payment values by type or by customer. Root cause There were no dashboard SQL queries, DTOs, service mappings, or export paths for the two member payment datasets. What was changed Added monthly payment totals by canonical payment type and by the top five clients plus Other Customers, including zero-filled ranges, aggregate and detail responses, CSV exports, Swagger metadata, and API documentation. Any added/updated tests Added and updated dashboard controller, service, and SQL tests for amount mapping, payment categories, customer ranking, zero filling, and CSV output.
PM-5719: Add member payment dashboard data
What was broken Unique Members Paid omitted projected TaaS, task, challenge, and engagement payments until they reached PAID status, making monthly and all-time metrics disagree with Wallet Admin. Challenge participation counted legacy resource imports in the import month, producing an April 2026 registrant spike. Root cause The payment query filtered to PAID and grouped by payout date. The participation query grouped resource and submission creation timestamps independently, although imported resources do not preserve their historical registration dates. What was changed Count the latest non-cancelled payment record in its creation month while retaining the existing payment buckets and Topgear exclusion. Cohort supported challenges by their latest actual phase completion date, then count unique submitter resources and same-challenge/member non-deleted submissions in that cohort. Any added/updated tests Updated dashboard SQL regression coverage for projected payment status/version/date semantics, supported challenge completion cohorts, linked submission membership, and removal of import/submission timestamp grouping. All 35 dashboard tests, lint, and build pass; the repository-wide suite still has 21 pre-existing failures in unchanged SFDC and report-directory specs.
PM-5703: correct dashboard payment and participation data
…lculations PM-5653 leaderboard calculations
What was broken The member payment dashboards omitted owed and on-hold July payments, leaving only an incorrect $51 contest total and no TAAS or engagement values. Root cause Both dashboard queries required PAID status and grouped values by payout date, unlike the established dashboard and Wallet Admin convention of using current non-cancelled payments in their creation month. What was changed Updated both payment-value queries to include latest non-cancelled payment records and group gross member amounts by payment creation month. Updated the dashboard documentation to describe the corrected projection semantics. Any added/updated tests Updated dashboard SQL regression coverage to require creation-month and non-cancelled selection for both payment charts and to reject PAID/date-paid filtering.
PM-5719: Include projected member payments
…lculations PM-5653 leaderboard calculations
…lculations PM-5653 - Round leaderboard points
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
2 participants
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.
PM-5719 - Add member payment dashboard data
PM-5703 - correct dashboard payment and participation data
PM-5653 - support leaderboard calculations
PM-5719 - Include projected member payments