Skip to content

#4458 executive summary schema changes - #4461

Open
staysgt wants to merge 9 commits into
developfrom
#4458-executive-summary-schema-changes
Open

#4458 executive summary schema changes#4461
staysgt wants to merge 9 commits into
developfrom
#4458-executive-summary-schema-changes

Conversation

@staysgt

@staysgt staysgt commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Changes

Schema changes, shared types, and seed data for executive summary dashboard.

Checklist

It can be helpful to check the Checks and Files changed tabs.
Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.

  • All commits are tagged with the ticket number
  • No linting errors / newline at end of file warnings
  • All code follows repository-configured prettier formatting
  • No merge conflicts
  • All checks passing
  • Screenshots of UI changes (see Screenshots section)
  • Remove any non-applicable sections of this template
  • Assign the PR to yourself
  • No yarn.lock changes (unless dependencies have changed)
  • Request reviewers & ping on Slack
  • PR is linked to the ticket (fill in the closes line below)

Closes #4458

@staysgt
staysgt force-pushed the #4458-executive-summary-schema-changes branch from 6960c15 to 8d66e8b Compare September 11, 2026 22:06
@staysgt staysgt self-assigned this Sep 12, 2026
@staysgt
staysgt marked this pull request as ready for review September 12, 2026 00:56
@staysgt
staysgt requested a review from wavehassman September 12, 2026 00:58
Comment thread src/backend/src/prisma/schema.prisma
Comment thread src/backend/src/prisma/schema.prisma Outdated
Comment thread src/backend/src/prisma/schema.prisma
Comment thread src/backend/src/prisma/schema.prisma Outdated
organization Organization @relation(fields: [organizationId], references: [organizationId])
seasonName String
seasonStartDate DateTime
seasonEndDate DateTime

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where are these 3 used?

I feel like we should just link this to car since each car is a new season

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I linked a car and got rid of the season name, but kept the seasonStartDate/endDate; I think those fields would be needed for calculating for some of the graphs. For example, the getBudgetSummary ticket needs to filter by dates. Maybe we could also have it just default like Aug-Aug, or whenever a season may actually run. Or the start/end date could also be attached to the car, which may make more sense

@staysgt
staysgt requested a review from wavehassman September 13, 2026 21:08
Comment thread src/backend/src/prisma/schema.prisma Outdated
Comment thread src/backend/src/prisma/schema.prisma
Comment thread src/backend/src/prisma/schema.prisma Outdated
@staysgt
staysgt requested a review from wavehassman September 13, 2026 22:14
Comment thread src/backend/src/prisma/schema.prisma Outdated
Comment thread src/backend/src/prisma/schema.prisma Outdated
Comment thread src/shared/src/types/exec-summary-shared-types.ts Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Executive Summaries] - Executive Summary Page Schema Changes

2 participants