Skip to content
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

Migrate Contracts and BLs from MAPS to OPS #3328

Open
11 tasks
jonnalley opened this issue Jan 20, 2025 · 0 comments
Open
11 tasks

Migrate Contracts and BLs from MAPS to OPS #3328

jonnalley opened this issue Jan 20, 2025 · 0 comments
Labels
draft draft only, not ready for prime time. still being authored or needs refinement story A defined user story adhering to expected norms including a narrative

Comments

@jonnalley
Copy link
Contributor

User Story

As an OPS user, I would like to have contracts and their budget lines that are/were present in MAPS available in OPS in order to manage them effectively within OPS.

Acceptance Criteria

  • The MAPS Projects provided by OPRE via spreadsheet are loaded into the OPS PROD DB.
  • The process should support upserting the data after the first run.
  • which contracts and BLs???

Tasks

UX

Dev

Definition of Done Checklist

  • UI works as designed (UX team)
  • Usability validated (UX team)
  • PR(s) have been merged to main
  • Design/tech debt eliminated
  • New design/tech debt documented (if applicable)
  • Build process updated
  • Documentation updated or added
  • Feature flags/toggles created

Additional Context & Resources

@jonnalley jonnalley added draft draft only, not ready for prime time. still being authored or needs refinement story A defined user story adhering to expected norms including a narrative labels Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft draft only, not ready for prime time. still being authored or needs refinement story A defined user story adhering to expected norms including a narrative
Projects
None yet
Development

No branches or pull requests

1 participant