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

Email call to action for Events #15725

Closed
9 of 10 tasks
jilladams opened this issue Oct 18, 2023 · 1 comment
Closed
9 of 10 tasks

Email call to action for Events #15725

jilladams opened this issue Oct 18, 2023 · 1 comment
Labels
Epic Issue type Events product maintained by Public Websites team Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide

Comments

@jilladams
Copy link
Contributor

jilladams commented Oct 18, 2023

User story

As an editor on https://prod.cms.va.gov/ creating a new Event, I would like attendees to RSVP by emailing an address such as VANJHCSCommsTeam [at] va.gov, so that I can manage RSVPs without a website.

Helpdesk description

Unfortunately, if an email address is added as the "Call to Action" URL without the mailto: prefix, it saves as /VANJHCSCommsTeam%40va.gov

Note: The help text for adding an Event "Call to Action" URL does not advise editors to add mailto: before email addresses.

This issue is inconvenient for site visitors who may wish to click the link to RSVP.

This issue also creates broken link alerts that are reported every 30-60 minutes in #content-broken-links until they are resolved by the editor or by a member of the VA Drupal CMS Help Desk team.

Tasks required

  • Design
  • Drupal
  • Front-end
  • Change management

Design

https://www.figma.com/file/8ZT1nnu8r2twbOlEhysnNp/Events?type=design&node-id=133-575&mode=design&t=GLTPkEbfBgSTUJDB-0

Launch plan

Launch plan

We don't want to expose the new Email field until FE can display that data in the template, and Editor communications have gone out to explain the new field.

  • Drupal changes are made but not merged
  • FE changes are made but not merged
  • Product works with VHA Digital Media (Justin Warren & Blake Scates) to:
    • Develop a communications plan (which might include an email to all VAMC editors)
    • Update existing Knowledge Base articles to explain the change
    • Comms are delivered with advance notice before the feature ships
  • Drupal changes can deploy
  • Any existing Events that include mailto: in URL are updated to use Email field instead.
  • FE changes can deploy
  • Change Management notice is sent that the feature is live
@jilladams jilladams added Epic Issue type Needs refining Issue status Events product maintained by Public Websites team Public Websites Scrum team in the Sitewide crew labels Oct 18, 2023
@jilladams
Copy link
Contributor Author

Doing an epic for this because of change management / launch steps are complex.

We need:

  • Change management ticket
  • Launch plan added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Issue type Events product maintained by Public Websites team Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide
Projects
None yet
Development

No branches or pull requests

1 participant