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

Execute additional BLs with decreased LoE on already-awarded agreement (contract mod process) #3152

Open
15 tasks
jonnalley opened this issue Dec 2, 2024 · 0 comments
Labels
design this is a design task 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 OPRE COR, I want to alter budget line(s) on an awarded contract in order to reflect a decreased LoE contract modification.

Preconditions

  • A contract exists with one or more BLs in Obligated status and with one or more BLs in Planned status

Acceptance Criteria

  • User can remove a budget line already in Planned status. <---we've never done removing/deleting BLs yet... :eyes? Is that allowed? zero out?
  • User can remove an entire services component? <--what happens to existing BLs on the SC?
  • The user could also decrease an existing Planned BL's amount in addition to or instead of removing a SC/BL mentioned in the previous AC while also requesting the status change of that BL to executing.
  • User can choose to move an existing Planned BL from one existing Services Component to another existing Services Component.
  • The above actions should be limited to current and existing restrictions on users possessing roles that can alter or request a BL status change.
  • Unlike a new contract entering the procurement process originally, the procurement tracker for these scenarios should be different.
  • All relevant event / history records should be recorded denoting the who (user), when, and what, and remote IP of changes being made/requested.

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 Dec 2, 2024
@jonnalley jonnalley added the design this is a design task label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design this is a design task 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