We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Conversation here: #5531 (comment)
In the VBA flow, input a phone number that's 3 digits long.
We should validate this field in a way that disallows 3 digit phone numbers.
No error will show (we're only enforcing a digit maximum right now).
N/A
Where is this issue occurring?
Version Number: Reproducible in staging?: Reproducible in production?: Logs: https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation Expensify/Expensify Issue URL: Issue reported by: Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered:
Triggered auto assignment to @michaelhaxhiu (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.
AutoAssignerTriage
Sorry, something went wrong.
Hey sorry for the spam @michaelhaxhiu, I'm just gonna do this one so no need for triage.
Luke9389
No branches or pull requests
Conversation here: #5531 (comment)
Action Performed:
In the VBA flow, input a phone number that's 3 digits long.
Expected Result:
We should validate this field in a way that disallows 3 digit phone numbers.
Actual Result:
No error will show (we're only enforcing a digit maximum right now).
Workaround:
N/A
Platform:
Where is this issue occurring?
Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: