Open m-natarajan opened 1 week ago
Triggered auto assignment to @JmillsExpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
@JmillsExpensify Huh... This is 4 days overdue. Who can take care of this?
Not sure if this is really a bug.
I can repro this. I shouldn't receive an email for my own custom subject comment I send.
Ah but isn't this simply because we are marking your own messages as unread for you? That's already being worked on.
Basically what I mean is, isn't this the same fundamental issue we're seeing with all Guide/sales/product reach outs, which also use the header and are marked as unread and notify the user sending the message.
Job added to Upwork: https://www.upwork.com/jobs/~021836887193135972228
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External
)
I chatted with Tom offline, and we agreed to get some feedback from the community on the root cause.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: Reproducible in staging?: Needs reproduction Reproducible in production?: Needs reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: @jamesdeanexpensify Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726009677714319
Action Performed:
Expected Result:
Message and email sent to receiver
Actual Result:
After sending a custom subject line message via New Expensify, it shows up in sender's (Gmail) inbox and looks like sender and receiver are same
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @hungvu193