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

Create module form alters to handle new Operating Status options (no op?) #19807

Open
13 tasks
jilladams opened this issue Nov 6, 2024 · 2 comments
Open
13 tasks
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

Comments

@jilladams
Copy link
Contributor

jilladams commented Nov 6, 2024

Description

For Operating Status with new options, we need to handle those options.

Engineering notes / background

  1. Add module form alters to account for new values in the Operating Status field

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.

  • Functional testing:
  • Code review:
  • Design review:
  • Accessibility review:
  • Product acceptance:

Acceptance criteria

ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable.

  • Existing Operating Status behavior is documented, tested, and not regressed
  • how do we verify form alters?
  • what's the more info open text AC?
  • CMS Feature toggle is created to show/hide the new values (is this actually possible for values on a field?)
  • Impact analysis is filled out and QA test plan is updated accordingly
  • Does this product have an existing regression test plan?
    • Yes, link:
    • No, regression test plan will be created as part of the work / points in this ticket
@jilladams jilladams changed the title Create module form alters to handle new Operating Status options Create module form alters to handle new Operating Status options and add CMS feature toggle Nov 6, 2024
@jilladams jilladams added VAMC CMS managed product owned by Facilities team Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team Vet Center CMS managed product owned by Facilities team labels Nov 6, 2024
@jilladams
Copy link
Contributor Author

This ticket could potentially be closed as a no op, once we complete story mapping and have designs in hand to understand how everything will change.

@jilladams
Copy link
Contributor Author

We need clarity on the Form alter piece of this, in order to say this ticket can be closed.

Discussion in Slack led to: no feature toggle, better change management instead, to keep this effort light. Removing toggle from this ticket.

🍌 Feature toggle, keep as list field. Adds significant engineering complexity in order to have a slightly better change management experience for editors
🍎 No feature toggle, just timing and change management. Is engineering light, but requires more detailed communication with editors around the timing of the launch

@jilladams jilladams changed the title Create module form alters to handle new Operating Status options and add CMS feature toggle Create module form alters to handle new Operating Status options Nov 6, 2024
@jilladams jilladams changed the title Create module form alters to handle new Operating Status options Create module form alters to handle new Operating Status options (no op?) Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant