-
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
Workspace - Spanish - Decimal separator comma is missing on the keyboard and dot is non functional on keyboard #10108
Comments
Triggered auto assignment to @yuwenmemon ( |
I've already found it check here this will be addressed in a followup PR. |
Okay great, assigning to you @Santhosh-Sellavel |
@Santhosh-Sellavel Eep! 4 days overdue now. Issues have feelings too... |
Not overdue |
@Santhosh-Sellavel Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Not overdue discussion going on in slack |
@Santhosh-Sellavel Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Not overdue |
Issue not reproducible during KI retests. (First week) |
@Santhosh-Sellavel 10 days overdue. Is anyone even seeing these? Hello? |
PR is live |
@Santhosh-Sellavel Eep! 4 days overdue now. Issues have feelings too... |
Not overdue PR is up |
@Santhosh-Sellavel Eep! 4 days overdue now. Issues have feelings too... |
@Santhosh-Sellavel Still overdue 6 days?! Let's take care of this! |
PR is up already |
@Santhosh-Sellavel Eep! 4 days overdue now. Issues have feelings too... |
PR is yet to be merged. |
@Santhosh-Sellavel Huh... This is 4 days overdue. Who can take care of this? |
Pr deployed |
@Santhosh-Sellavel Huh... This is 4 days overdue. Who can take care of this? |
PR is deployed |
@Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@Santhosh-Sellavel Still overdue 6 days?! Let's take care of this! |
@Santhosh-Sellavel 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Fixed now, and should be closed! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue found when executing #9800
Action Performed:
Expected Result:
Verify that it's possible to enter a decimal number with three digits after the comma into Rate input
Actual Result:
Impossible to enter a decimal number into Rate input since comma is not available in the keyboard. The dot is non functional on the keyboard.
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.86-1
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: