Skip to content

feat: add govDelivery listing opportunity email#6503

Open
ludtkemorgan wants to merge 5 commits into
mainfrom
6220/govDelivery
Open

feat: add govDelivery listing opportunity email#6503
ludtkemorgan wants to merge 5 commits into
mainfrom
6220/govDelivery

Conversation

@ludtkemorgan

Copy link
Copy Markdown
Collaborator

This PR addresses #6220

  • Addresses the issue in full
  • Addresses only certain aspects of the issue

Description

Doorway has the same listing opportunity email that is in core except it goes through govDelivery rather than directly through the email service.

This PR does the following:

  • Adds a govDelivery service to be able to send bulletins to defined lists
  • sends the listing opportunity email via govDelivery if enableListingOpportunity feature flag is enabled
  • Updates the listing opportunity email to have features only seen in Doorway:
    • Disclaimer text below the apply buttons
    • Additional footer text
    • Bolded the due date field - This has been done everywhere

Open questions:

  1. The time has been added to the due date field ("May 19, 2026 at 3:00pm PDT" instead of "May 19, 2026"). I added it for all cases, but need to get verification that that can be done for LA.

How Can This Be Tested/Reviewed?

This is hard to test without access to govDelivery. You can work with Morgan to get added to the staging govDelivery list

The "New Rental Opportunity" email with correct content should be sent in the following scenarios:

  1. when a listing is created and the status is "active"
  2. when a listing is updated and the status is "active" when it previously wasn't ("publish" the listing)

Author Checklist:

  • Added QA notes to the issue with applicable URLs
  • Reviewed in a desktop view
  • Reviewed in a mobile view
  • Reviewed considering accessibility
  • Added tests covering the changes
  • Made corresponding changes to the documentation
  • Ran yarn generate:client and/or created a migration when required

Review Process:

  • Read and understand the issue
  • Ensure the author has added QA notes
  • Review the code itself from a style point of view
  • Pull the changes down locally and test that the acceptance criteria is met
  • Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

@netlify

netlify Bot commented Jul 14, 2026

Copy link
Copy Markdown

Deploy Preview for bloom-angelopolis ready!

Name Link
🔨 Latest commit 4d49ff1
🔍 Latest deploy log https://app.netlify.com/projects/bloom-angelopolis/deploys/6a57d8a9f427000008ffd315
😎 Deploy Preview https://deploy-preview-6503--bloom-angelopolis.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 14, 2026

Copy link
Copy Markdown

Deploy Preview for partners-bloom-dev ready!

Name Link
🔨 Latest commit 4d49ff1
🔍 Latest deploy log https://app.netlify.com/projects/partners-bloom-dev/deploys/6a57d8a94c7cfb0008f7905c
😎 Deploy Preview https://deploy-preview-6503--partners-bloom-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 14, 2026

Copy link
Copy Markdown

Deploy Preview for bloom-exygy-dev ready!

Name Link
🔨 Latest commit 4d49ff1
🔍 Latest deploy log https://app.netlify.com/projects/bloom-exygy-dev/deploys/6a57d8a9ffae2e000872851a
😎 Deploy Preview https://deploy-preview-6503--bloom-exygy-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant