-
Notifications
You must be signed in to change notification settings - Fork 69
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
[ADD] VBA terms (batch 3) to Service taxonomy name #17060
Comments
@davidmpickett, can we please move forward with the following benefit services
and hold the following with a plan to reassess as the roll-out proceeds
|
@mmiddaugh Okay, I split off Creating an Account & Fiduciary into their own tickets.
I assume that this ticket would be a priority for Sprint 1 over #16906? This is a 2-pointer so I feel comfortable committing to it. cc @jilladams |
@mmiddaugh I have drafted subfield content for all three Services in Drupal. Once again I have marked these as "In Review". You can move them to Published at your discretion. Some notes:
I will also update these on the VBA and CAIA review tickets. |
|
Good catch. I was using a static copy of the spreadsheet and it didn't have that update. That was actually a change I suggested to expand on what was copy edited by CAIA. However, I have taken this language verbatim from the Pre-need page, so I think we can consider it copy edited enough for this pass (while still giving them the final review opportunity) |
@mmiddaugh FYI I tweaked the pre-need description a hair "We can help you apply in advance to be buried in a VA national cemetery. This can help make the burial planning process easier for your family members in their time of need." |
Related tickets updated |
Which Taxonomy is this term for?
VA services taxonomy
Proposed term name/label
Does this overlap with any existing term in the taxonomy?
No
Rationale for adding this term
Follow up from #16269
Which products will this term impact?
VBA Regional Office
Have stakeholders from impacted products been consulted?
Yes
Have you drafted content for all the relevant subfields?
Some, but not all
Acceptance Criteria
The text was updated successfully, but these errors were encountered: