-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPIKE: Investigate Migration of Direct Deposit Functionality #7998
Comments
cc: @jperk51 FYI while you were out |
@kpethtel : Just an FYI. Added to backlog. Looks like this one is more Q2 |
@jperk51 If you agree, I think the work being done in ticket 8332 covers this and we can close and link these. cc: @aherzberg |
Yeah, the other ticket has some more info on it and is referring to the same migration. I agree we should close this one. |
Closing this ticket. #8332 will be the reference point |
Description
Investigation Story: Investigate the Migration Effort for Direct Deposit Functionality and possible API/BE Impacts.
**This would be slated for Q2 and more information on what the Feature Development can be found HERE
Summary from about what we know so far
Education business at VA is migrating their direct deposit functionality into the same backend that supports the comp & pen direct deposit information. They are starting with Chapter 33 (GI Bill) benefits, and then migrating the other education benefits over a number of years.
The initial part of this migration is set to be completed by April 20. This affects a number of other parts of VA.gov as well, including: The VA.gov profile
** Original Information Reference Threads:**
https://dsva.slack.com/archives/C03P6C3FYMR/p1707946761775159
https://adhoc.slack.com/archives/C0206QFMXFU/p1707947793953569
## Acceptance Criteria
The text was updated successfully, but these errors were encountered: