-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Expensify cash is mentioned in Email notification #4223
Comments
Triggered auto assignment to @timszot ( |
This will have to be handled internally since our notifications are handled there. |
Triggered auto assignment to @zsgreenwald ( |
What do we want it to say? "head over to the New Expensify" ? "head over to new.expensify.com"? |
Felt like this was worth discussing, so I brought it up here. |
Personally, I'd lean on just calling it "Expensify", but let's see what the room thinks. |
So far, consensus is to just call it "Expensify" and hyperlink new.expensify.com. Going to give it 24 hours, but I'll update you if we head in a different direction. |
Confirmed here, the proper copy should be:
|
@isagoico Let me know if you need help with anything else! |
Looks like this issue is ready to be worked on! I'll re add the engineering label. |
Triggered auto assignment to @deetergp ( |
WAT? Take a hike @MelvinBot, this has a PR and is pending review! |
Don't know why this did not auto-close but it has been deployed to production. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Email should mention to navigate to New Expensify to answer the message.
Actual Result:
Email mentions to navigate to Expensify.cash to answer the message
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.0.80-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: