Ticket #2157: Use creator email rather than submitters for status updates / domain request

[zandercymatics]

Ticket

Resolves #2157

Changes

• For status change emails, we now send an email to self.creator rather than self.submitter when the flag "profile feature" is on
• Added onto existing unit tests and added one to test the flag

Context for reviewers

This PR will send an email to the domain request creator rather than the submitter only if the profile feature flag is enabled

Setup

For all of the steps below, make sure both the creator and submitter have emails that you are in control of

1. Change the status of any domain request with the profile flag OFF. You should expect an email to the submitter email
2. Change the status of any domain request with the profile flag ON. You should expect an email to the creator email

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

• [ ] Met the acceptance criteria, or will meet them in a subsequent PR
• [ ] Created/modified automated tests
• [ ] Added at least 2 developers as PR reviewers (only 1 will need to approve)
• [ ] Messaged on Slack or in standup to notify the team that a PR is ready for review
• [ ] Changes to “how we do things” are documented in READMEs and or onboarding guide
• [ ] If any model was updated to modify/add/delete columns, makemigrations was ran and the associated migrations file has been commited.

Ensured code standards are met (Original Developer)

• [ ] All new functions and methods are commented using plain language
• [ ] Did dependency updates in Pipfile also get changed in requirements.txt?
• [ ] Interactions with external systems are wrapped in try/except
• [ ] Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

• [ ] New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• [ ] Checked keyboard navigability
• [ ] Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
• [ ] Add at least 1 designer as PR reviewer

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

• [ ] Pulled this branch locally and tested it
• [ ] Reviewed this code and left comments
• [ ] Checked that all code is adequately covered by tests
• [ ] Made it clear which comments need to be addressed before this work is merged
• [ ] If any model was updated to modify/add/delete columns, makemigrations was ran and the associated migrations file has been commited.

Ensured code standards are met (Code reviewer)

• [ ] All new functions and methods are commented using plain language
• [ ] Interactions with external systems are wrapped in try/except
• [ ] Error handling exists for unusual or missing values
• [ ] (Rarely needed) Did dependency updates in Pipfile also get changed in requirements.txt?

Validated user-facing changes as a developer

• [ ] New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing

• [ ] Checked keyboard navigability

• [ ] Meets all designs and user flows provided by design/product

• [ ] Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

• [ ] Tested with multiple browsers, the suggestion is to use ones that the developer didn't (check off which ones were used)

  • [ ] Chrome
  • [ ] Microsoft Edge
  • [ ] FireFox
  • [ ] Safari

• [ ] (Rarely needed) Tested as both an analyst and applicant user

Note: Multiple code reviewers can share the checklists above, a second reviewers should not make a duplicate checklist

As a designer reviewer, I have

Verified that the changes match the design intention

• [ ] Checked that the design translated visually
• [ ] Checked behavior
• [ ] Checked different states (empty, one, some, error)
• [ ] Checked for landmarks, page heading structure, and links
• [ ] Tried to break the intended flow

Validated user-facing changes as a designer

• [ ] Checked keyboard navigability

• [ ] Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

• [ ] Tested with multiple browsers (check off which ones were used)

  • [ ] Chrome
  • [ ] Microsoft Edge
  • [ ] FireFox
  • [ ] Safari

• [ ] (Rarely needed) Tested as both an analyst and applicant user

Screenshots

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.

[zandercymatics]

@CocoByte Should be on getgov-hotgov!

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.

[zandercymatics]

@abroddrick While unrelated, it looks like that bug is coming from some failing js in our get-gov-admin.js file.

Since select-2 uses AJAX to grab its data, this is causing a fail condition on the creator field when you try to access it. I can only repliclate this locally - I do not entirely understand why but it likely is just script load order. I've include some error handling in the failing area of the script (it was missing that anyway)

[github-actions[bot]]

🥳 Successfully deployed to developer sandbox za.