-
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
Billing Address field in AddDebitCardPage doesn't accept text #14918
Comments
Triggered auto assignment to @mallenexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @grgia ( |
Removing @grgia because @hayata-suenaga is working on it and I think he already found the cause |
|
Can you confirm what versions this is happening on, we just had a deploy so I want to know if this is in production now or the fresh new staging. In which case it would not be a deploy blocker. |
Job added to Upwork: https://www.upwork.com/jobs/~011c6f32902f1a74c9 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @parasharrajat ( |
|
@mountiny I tested with version v1.2.65-2 |
Ok yeah so that is production now so this does not have to be a deploy blocker! But I think we should still CP to Staging the fix so this gets out sooner |
This issue is being held until the QA can have a test debit card to implement the above testing steps. |
Issue about testing debit card credential for QA: https://github.com/Expensify/Expensify/issues/226985 |
I thought if the issue title has [HOLD], melvin-bot will be chill. does anyone know if we created a test card for QA team to use? |
No, HOLD does not stop melvin, only Reviewing does, but that should only be used for actual PR being in a review. You can also change the priority of the issue if appropriate |
I think Applause has the ability to test with cards now: https://github.com/Expensify/Expensify/issues/226985#issuecomment-1502170174 @hayata-suenaga we should be able to proceed with updating the test: #14918 (comment) |
Dropped in #qa to ask about getting this tested |
Has the comment already been updated? |
👋 Noticed this in the +4 weeks old WAQ dashboard. There isn't a hold in the title anymore, dropping back to |
Sorry, which comment? |
@aldo-expensify nvm I was confused between updating testing steps in the original comment and actual Applause tests 😅 |
@mvtglobally can you test this? Here's Maria's reply in #QA
|
I will update in the morning with details |
Thanks @mvtglobally , I'm going to close then. Comment/reopen if needed. |
@mallenexpensify @aldo-expensify @hayata-suenaga Be sure to fill out the Contact List! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Break down in numbered steps
Expected Result:
Inputted text should be displayed.
Actual Result:
Text doesn't appear when text is inputted.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
I tried to paste a text in the field instead of typing, but it doesn't work either. No workaround found.
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation: https://expensify.slack.com/archives/C03TQ48KC/p1675793090919109
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: