-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add OldDot's default output currency setting to NewDot #52769
Comments
Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new. |
@jamesdeanexpensify any feedback on the text on either of these screens? Keeping internal until we align on the solution. |
Thoughts on:
|
Going to think on this one a little more. It's a bit tricky. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Add OldDot's default output currency setting to NewDot What is the root cause of that problem?New feature What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)NA ResultScreen.Recording.2024-11-21.at.17.18.15.mov |
@JmillsExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Still in planning |
@JmillsExpensify Huh... This is 4 days overdue. Who can take care of this? |
@JmillsExpensify Still overdue 6 days?! Let's take care of this! |
still in the queue |
@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too... |
Same as above |
@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too... |
@JmillsExpensify Still overdue 6 days?! Let's take care of this! |
Still not a priority |
@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too... |
@JmillsExpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Problem
NewDot trial users have consistently run into an issue where they sign up in a certain country – for instance, Spain and EUR – but their employer uses a different currency and expects all reports to be submitted in that same currency. This not only creates confusion, but it's detrimental to our bottom-up conversation overall.
Solution
For consistency with OldDot and to increase our changes that bottom-up flows work without a hitch, let's add a
Payment currency
setting to NewDot. This is equivalent to theReport Currency
setting in OldDot'spersonal
type policy, and functions exactly the same – meaningly, this sets the currency all expenses on a report should be converted to.In NewDot the setting will look like this.
The text was updated successfully, but these errors were encountered: