Repository navigation
Workspace - Spanish - Decimal separator comma is missing on the keyboard and dot is non functional on keyboard #10108
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue found when executing #9800
Action Performed:
- Launch App and login with Expensify account
- Change language to Spanish
- Open Settings > Workspace > Reimburse expenses
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?
- Mobile Web
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:
Activity
melvin-bot commentedon Jul 26, 2022
Triggered auto assignment to @yuwenmemon (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.Santhosh-Sellavel commentedon Jul 26, 2022
I've already found it check here this will be addressed in a followup PR.
yuwenmemon commentedon Jul 26, 2022
Okay great, assigning to you @Santhosh-Sellavel
melvin-bot commentedon Aug 1, 2022
@Santhosh-Sellavel Eep! 4 days overdue now. Issues have feelings too...
Santhosh-Sellavel commentedon Aug 1, 2022
Not overdue
melvin-bot commentedon Aug 5, 2022
@Santhosh-Sellavel Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Santhosh-Sellavel commentedon Aug 5, 2022
Not overdue discussion going on in slack
25 remaining items
Santhosh-Sellavel commentedon Sep 20, 2022
Pr deployed
melvin-bot commentedon Sep 26, 2022
@Santhosh-Sellavel Huh... This is 4 days overdue. Who can take care of this?
Santhosh-Sellavel commentedon Sep 26, 2022
PR is deployed
melvin-bot commentedon Sep 30, 2022
@Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Oct 4, 2022
@Santhosh-Sellavel Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Oct 6, 2022
@Santhosh-Sellavel 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
melvin-bot commentedon Oct 6, 2022
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.
Santhosh-Sellavel commentedon Oct 6, 2022
Fixed now, and should be closed!
Put every numeric field behind one component