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 modified LoE on already-awarded agreement (contract mod process) #3072

Open
15 tasks
jonnalley opened this issue Nov 14, 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

jonnalley commented Nov 14, 2024

User Story

As an OPRE COR, I want to alter budget line(s) on an awarded contract in order to reflect a modified 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 add an existing services component and a budget line on that new services component on an existing awarded contract. The user should then be able to request these budget lines go into executing status. This action should be limited to current and existing restrictions on users possessing roles that can request a BL status change.

  • The user could also increase an existing Planned BL's amount in addition to or instead of adding the new SC/BL mentioned in the previous AC while also requesting the status change to executing

  • User can remove a budget line already in Planned status. We've never done removing/deleting BLs yet... 👀 ? 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.

  • Unlike a new contract entering the procurement process originally, the procurement tracker for these new BLs going into executing status 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 design this is a design task labels Nov 14, 2024
@jonnalley jonnalley changed the title Execute additional BLs with modifications on already-awarded agreement (contract mod process) Execute additional BLs with increased LoE on already-awarded agreement (contract mod process) Dec 2, 2024
@jonnalley jonnalley changed the title Execute additional BLs with increased LoE on already-awarded agreement (contract mod process) Execute additional BLs with modified LoE on already-awarded agreement (contract mod process) Dec 3, 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