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

Start a Contract Modification for a Modified LOE #3268

Open
5 of 26 tasks
kimschulke opened this issue Jan 6, 2025 · 4 comments
Open
5 of 26 tasks

Start a Contract Modification for a Modified LOE #3268

kimschulke opened this issue Jan 6, 2025 · 4 comments
Labels
dev backend ready Backend, Pipeline, or other backend work is refined, and ready for Developers to begin. dev frontend ready Designers have created the designs, story has been refined, and ready for a Developer to begin story A defined user story adhering to expected norms including a narrative

Comments

@kimschulke
Copy link
Contributor

kimschulke commented Jan 6, 2025

User Story

As a COR I want to start a Contract Modification for a Modified Level of Effort so that my edits in OPS can be officially updated on the Award documents

Acceptance Criteria

  • User can see the edit they made on a BL or SC that triggered the Modified Level of Effort listed under "Edits That Require a Contract Modification" on the Award & Modifications Tab
  • User can click Start Modification on the Award & Modifications Tab
  • User can review the details of the agreement
  • User can select Planned BLs to Execute (if applicable)
  • User cannot select Draft and Obligated BLs (disabled with tooltip)
  • User can Review CANs to see the impact on the CAN/budget for any BLs selcted
  • User can review the summary of their contract modification including the details of their modified LOE (which BLs or SCs were changed)
  • User can upload any relevant documents, as needed
  • User can provide optional notes to the approver, as needed
  • User can click "Send to Approval" to send the mod to their DD
  • All relevant alerts are displayed as changes are successfully sent to approval, In Review, and either approved or declined
  • All modified LOE changes included in the mod appear with an In Review status
  • 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

  • Explore design options
  • Share design options for feedback with team
  • Share design options with OPRE
  • Refine design based on feedback
  • Provide designs on Ready for Dev with necessary annotations and business rules

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
Copy link
Contributor

Is this a dupe of #3072 ?

@kimschulke
Copy link
Contributor Author

@jonnalley this is not a dupe of #3072. #3072 is when the user edits the BLs in OPS and #3268 is when they actually start the modification process

@jonnalley
Copy link
Contributor

@kimschulke ok, thank you! I probably need to brush up on the changes to the interactions and designs in Figma.

@jonnalley jonnalley added story A defined user story adhering to expected norms including a narrative draft draft only, not ready for prime time. still being authored or needs refinement labels Jan 9, 2025
@kimschulke
Copy link
Contributor Author

@jonnalley I am happy to walk through the designs with you if you want to attempt the github mapping together

@kimschulke kimschulke added dev frontend ready Designers have created the designs, story has been refined, and ready for a Developer to begin dev backend ready Backend, Pipeline, or other backend work is refined, and ready for Developers to begin. and removed draft draft only, not ready for prime time. still being authored or needs refinement labels Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev backend ready Backend, Pipeline, or other backend work is refined, and ready for Developers to begin. dev frontend ready Designers have created the designs, story has been refined, and ready for a Developer to begin story A defined user story adhering to expected norms including a narrative
Projects
None yet
Development

No branches or pull requests

2 participants