Create module form alters to handle new Operating Status options (no op?) #19807
Labels
Facilities
Facilities products (VAMC, Vet Center, etc)
Needs refining
Issue status
Regional office
CMS managed VBA product owned by the Facilities team
sitewide
VAMC
CMS managed product owned by Facilities team
Vet Center
CMS managed product owned by Facilities team
Description
For Operating Status with new options, we need to handle those options.
Engineering notes / background
Testing & QA
Scope / Impact analysis
What, if anything, could break as a result of this change?
Engineer should assess this when approaching PR.
Roles / assignments
After functional testing, code review, accessibility review, and design review can happen in parallel.
Acceptance criteria
ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable.
The text was updated successfully, but these errors were encountered: