Skip to content

feat: mp 2561 future years goals#6775

Open
infante-jaime wants to merge 9 commits intomainfrom
feature/mp-2561-future-years-goals
Open

feat: mp 2561 future years goals#6775
infante-jaime wants to merge 9 commits intomainfrom
feature/mp-2561-future-years-goals

Conversation

@infante-jaime
Copy link
Contributor

@infante-jaime infante-jaime commented Mar 25, 2026

https://kiva.atlassian.net/browse/MP-2594

Added support for the annual goal reset to work beyond 2026. The toast and "Set goal" card now always display the current year dynamically, so the same behavior users experienced on Jan 1, 2026 will repeat automatically every year going forward.

What happens on Jan 1 of each new year:

  • The active goal from the previous year expires and disappears
  • A toast appears prompting the user to set a new goal for the current year
  • The create-goal card becomes visible showing the current year

To test:

  • Visit /mykiva?renewYear=2027 to simulate the Jan 2027 reset — your active 2026 goal will expire, the toast will say "It's time for your 2027 impact goal", and the create-goal card will appear
  • Change to renewYear=2028 to verify the cycle continues year over year

Things to keep in mind:

  • The "Set goal" card always pulls the year from the system clock, so it will show the real current year regardless of the renewYear param
  • To fully test future year scenarios (e.g. a 2027 goal expiring in 2028), the goal needs to be created directly via the API with the desired dateStarted, since the UI always stamps today's date when creating a goal

@infante-jaime infante-jaime changed the title Feature/mp 2561 future years goals feat: mp 2561 future years goals Mar 25, 2026
isNextStepsRoute() {
return this.$route.path === '/mykiva/next-steps';
},
goalsV2Enabled() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Looks like some regression in this branch related to recent changes to remove old experiment flags. Please take a look at main and remove code that is no longer needed.

@infante-jaime infante-jaime requested a review from a team March 25, 2026 22:22
Copy link
Collaborator

@dyersituations dyersituations left a comment

Choose a reason for hiding this comment

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

See my comment about merge regressions @infante-jaime

@infante-jaime
Copy link
Contributor Author

yes currently working on removing the extra code from my bad merge

@infante-jaime infante-jaime marked this pull request as draft March 25, 2026 22:54
@infante-jaime infante-jaime marked this pull request as ready for review March 26, 2026 01:15
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.

2 participants