Open TroyA6 opened 7 months ago
@jilladams Can we work through this one together so I know what to do with requests like this? Thanks in advance!
Sure thing, Fran!
First though: @TroyA6 can you confirm if Dave already approved this CLP? (I don't have JIRA permissions anymore, so if he approved there, can't see it.)
ALso: this looks like a duplicate of #13603 , related to the Helpdesk ticket https://va-gov.atlassian.net/browse/VAHELP-5758. On that ticket where this CLP node (https://prod.cms.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials) was originally created, Danielle Thierry had marked it blocked while they worked on a comms plan.
@TroyA6 I'm gonna bump that other ticket to check in with Danielle, but I think it would prob be most helpful if you can share whatever message you got from Carl Dickerson in VAHELP-6762, to help us connect the dots. Thanks!
Gonna go ahead and close this as a dupe, and will tag you in on #13603.
@jilladams Not much to share from Carl: Components
Campaign Landing Page Where on the site is the issue occurring? (Please paste a direct link - thank you!)
https://www.va.gov/initiatives/sign-in-securely-with-logingov/ Description
Hi,
I am a member of VA OCTO Login.gov adoption team. We would like to request a new CLP to support our ongoing work to migrate Veterans to more secure sign-in credentials. This work is supported by Danielle Thierry and Dave Conlon (we have approvals on both ends).
Can you please CC replies to Lauren.Morris3@va.gov and Sophia.Philip@VA.gov.
Reopening based on conversation on #13603
@DanielleThierryUSDSVA @mnorthuis can the 2 of you help confirm the redirect needs here? 2 questions:
Drupal: https://prod.cms.va.gov/initiatives/sign-in-securely-with-logingov FE: https://www.va.gov/initiatives/sign-in-securely-with-logingov
Will that CLP be archived, kept in place as is, or redirected to the new CLP?
Node: https://prod.cms.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials FE: (not published yet): https://www.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials
Will this CLP require a vanity URL? If so, what will it be?
Thanks!
cc @CarlDickerson
Hi @jilladams! Our OCTO team has decided on a vanity URL for the new CLP: https://va.gov/sign-in-changes
In reviewing the content for the new CLP, I've also edited the H1. So the new FE URL will be: https://va.gov/initiatives/prepare-for-vas-secure-sign-in-changes
We'll want to redirect the older CLP (https://www.va.gov/initiatives/sign-in-securely-with-logingov) to this new CLP, yes.
cc @mnorthuis @jennymayoco @kristinoletmuskat @CarlDickerson
Thanks Danielle! I created #16494 to track those 2 redirects. Can you clarify if those redirect plans are already vetted by IA? (cc @mnorthuis @jennymayoco)
Thank you, @jilladams! Yes, @mnorthuis and I confirmed the URL together.
@jilladams have we reached a point in in-take where the page in Drupal can be shared with my team for updates and edits?
The new page exists in the CMS: https://prod.cms.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials, and you should already be able to access that to make edits. @DanielleThierryUSDSVA I see that you've made some changes in there already -- feel free to flag if you have any concerns about Carl making edits.
Thanks, @jilladams!
@CarlDickerson As I am editing the draft content your team shared with me, I'm adding it to the Drupal page to help make sure my edited content fits within the templates' character counts and to help visualize the content on the page. Please don't edit the content I'm adding. If you want to add more draft content, that's great, and I can edit right in Drupal. Just let me know before you go into the page so we're not running into each other in there. Thanks.
@DanielleThierryUSDSVA @CarlDickerson I'm backlog grooming and just checking on the status of this ticket. Thanks in advance! cc @jilladams
Hi @FranECross. Thanks very much for checking in.
@DanielleThierryUSDSVA Thanks for much for the quick response! Much appreciated. We'll await instructions as they come in.
Jira ticket: https://va-gov.atlassian.net/browse/VAHELP-6762
Status
Description
Requested by carl.dickerson@va.gov with support from Danielle Thierry and Dave Conlon (approvals on both ends). To clarify this request, we are needing setup for a new CLP. The url provided in the helpdesk ticket is for a page that will no longer be in use (it was a required field in the ticket). We will need a new URL and after discussing with Dave Conlon and Danielle Thierry, we were told it would be best to request a brand new CLP. If you could assist us in getting a Github ticket started as soon as possible, that would be helpful.
Intake
[x] What triggered this runbook? Help desk ticket VAHELP-6762
[x] Link to associated JIRA help desk ticket (if applicable) Help desk ticket: VAHELP-6762
[x] Vanity URL requested:
[x] Name of submitter (if applicable) Submitter: Carl Dickerson (carl.dickerson@va.gov)
Acceptance criteria
If approved Additional Approval not needed
Helpdesk steps
NEW CLP node link = https://prod.cms.va.gov/initiatives/migrating-veterans-accounts-to-more-secure-sign-in-credentials
Public Websites steps
https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16494
[x] @mention Mikki Northuis in IA (#sitewide-content-ia) with link to Github issue, to provide Vanity URL request feedback. IA must review & approve URL requests.
[x] When approved by IA, execute the steps of the URL change request ticket from step 2 above.
[ ] When redirect is verified in Production, close Redirect ticket as well as this ticket.