Step 3 of Executing BLs - Solicitation

User Story

As a COR, I need to update and advance a contract through the Soliciation milestone of an executing contract so that OPRE can track when the procurement shop has recieved all bids.

Preconditions

A contract has one or more budget line in Executing status and the contract has already advanced past the second milestone.

Acceptance Criteria

[ ] The user can see a visual understanding of the overall procurement process and the current progress in it
[ ] The user can optionally choose a target completion date and optionally commit the input of only that information and nothing else--independent of other user input.
[ ] The user can attest that the solicitation is closed to vendors
[ ] The user can select the OPS user who attests to this and the date that this was completed. The date must either be the current or a prior date.
[ ] The user can optionally provide any notes limited to 750 characters
[ ] The user can reset all user input
[ ] The user can commit their input which will advance the contract to to the next milestone.
[ ] If any error is encountered in persisting the change(s), that error should be presented to the user
[ ] The relevant entries should be recorded in the event/history table(s) and be able to be properly rendered properly in the history of changes to the agreement

Tasks

UX

[x] Review design options with team
[x] Review design with stakeholders
[x] Refine steps with stakeholders
[x] Provide designs to developers

Dev

Definition of Done Checklist

[ ] Usability validated
[ ] UI works as designed
[ ] 90%+ Code coverage achieved
[ ] PR(s) have been merged to main
[ ] Design/tech debt eliminated
[ ] Build process updated
[ ] Documentation updated or added
[ ] Feature flags/toggles created

Additional Context & Resources

A story pertaining to the prior step in the contract's lifecycle is #1501

HHS / OPRE-OPS

Step 3 of Executing BLs - Solicitation #1106