Skip to content

DRAFT: Repair direct message recipients and copy curator team email addresses #2325

Description

@matthewjchandler

User Story

As a moderator/curator, I need to see a record of all messages sent to submitters/depositors in my shared team email account, so that I can monitor activity, verify which messages were sent in case of questions, and coordinate curation handoffs as needed.

Current Behavior

The recent tickets to update messages to submitters/depositors (#2207, #2208, #2209, and #2210) all included a criterion to send to the submitter/depositor only. However, each message type ended up being sent to moderators as well, with the moderator named as the recipient in each outgoing message by mistake. #2299 addresses that bug for review messages specifically, but the 3 other message types still need remediation.

For example, the New Submission Message:

Image

Desired Behavior

Messages intended for submitters/depositors should be addressed to the submitter/depositor by name and only sent directly to that person's email account (using the "to" field in an email). Each message should also be silently copied to the appropriate curator team email account--using the "bcc" field in the email, so that the curators can see who the direct recipient of each message was, but the direct recipient does not see that the message was copied to the curators (and get confused about reply options when the sender is a no-reply address). The appropriate curator team email address is determined by the group a given work is assigned to.

For example, a revised New Submission Message:

Image

Acceptance Criteria

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementunder-po-reviewTickets that are under review by the PO for whether they should be considered for work or not

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions