Redirect URL /records to /medical-records (when MR phase 1 reaches 100%)

[sterkenburgsara]

Description

When MR reaches 100%, the temp MR landing page will have no purpose and we need to redirect this page to the correct one.

User story

As a Veteran, I want to be able to get to Medical Records on VA.gov if I click an old URL that I have saved in a bookmark or elsewhere, so that I can still continue on and manage my care.

Notes

• UPDATE: as of 11/25, teams are expected to do our own redirects. see slack post
• Estimated timing: MR Ph1 staging review is Dec 18, should launch soon after actual launch was 12/20.

Possible tasks:

• Read VA Platform: VA.gov to VA.gov Redirect
• Confirm with Sitewide Content, Accessibility, Information Architecture team (CAIA) that our team puts in a request to another team rather than open our own PR

Acceptance criteria

• URL va.gov/my-health/records/ redirects to va.gov/my-health/medical-records
• QA review

[wesrowe]

@sterkenburgsara, are you sure that CAIA needs to be involved in this redirect? Carlos thinks we could do it ourselves easily.

[kjsuarez]

CAIA redirect request

[wesrowe]

@kjsuarez, I see your CAIA request ticket. Are you moving into implementation? The funny thing here is that Sara is our IA specialist, so you don't need CAIA's approval to implement the redirect. [edit:] Mikki clarified that CAIA is a PR reviewer for all redirects. (Still not quite sure if we needed to trigger any additional review with the ticket above; but I don't expect us to be doing these very often so no big deal.)

EDIT: I see that the notes in the ticket body are clear, but the possible task is not as accurate. Or rather, we already confirmed we have to actually do the implementation.

[kjsuarez]

@wesrowe I understand that I need to do the implementation. Based on the documentation referenced in the slack post linked above, it seemed like we needed a CAIA approval before implementation. If that's not the case I'll go ahead and make the code change now.

[kjsuarez]

PR

[mnorthuis]

@wesrowe FYSA, all redirects need approval from Sitewide IA (currently CAIA) - that is the team that vets and approves, regardless of the reason its being done. We are also approvers on the PR. This is to ensure the redirect is necessary, is documented, is valid, and kicks off any content work needed...among other reasons.

@kjsuarez @sterkenburgsara I approved the PR so you can move forward. We don't review code, so just wanted to drop a note to make sure all child URLs are being handled appropriately so there won't be any other pages with the /records sub-directory.

[mcarterA6]

@allanto-ah - Would you be able to validate this in the appropriate environment?

[allanto-ah]

@mcarterA6 Yes I should be able to do this in staging

[sterkenburgsara]

Confirmed there are no child URLs under this directory. Only the /records page needs to be redirected.

[mcarterA6]

Need to confirm when this will be deployed.
@wesrowe will check with the public websites team to confirm deployment schedule.

[mcarterA6]

Marked as blocked until we confirm when this will be moved to production.

[wesrowe]

Friend of the team Jill Adams pointed me to this deployment log for the devops repo. It appears to have been releasing over the holiday break, but we would probably have to look deeper to see if Kevin's PR went.

I just tried in staging, the redirect is NOT in place there yet.