-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$250] Changing "Purchase bill date" clears "Purchase bill status" Authorised value #42317
Comments
Triggered auto assignment to @greg-schroeder ( |
@greg-schroeder Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Job added to Upwork: https://www.upwork.com/jobs/~011cccc97f51a7d2bb |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha ( |
Adding to #wave-collect as this is a Xero bug |
ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
App/src/pages/workspace/accounting/xero/export/XeroExportConfigurationPage.tsx Lines 61 to 62 in a905b59
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)NA |
Trying to reproduce the issue |
🎀 👀 🎀 |
Triggered auto assignment to @luacmartins, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@luacmartins could you please check if this is something we can fix on the BE? thanks! #42317 (comment) |
Yea, this seems like internal work cc @lakchote |
@luacmartins, @greg-schroeder, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick! |
This is internal, no update just yet - @lakchote are you across this? |
@greg-schroeder @luacmartins @kavimuru @getusha not a bug, and no BE fix needed. Testing needed to be done on the ad hoc build, since there was the merge freeze. You can test it out here: https://42340.pr-testing.expensify.com/ (PR) I've tested it there, and the value for |
Nice, so can we just close this issue then? |
Yes, I'm closing it |
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 validating #41583
Version Number: 1.4.74-2
Reproducible in staging?: y
Reproducible in production?: new feature
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
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Expected Result:
The value shouldn't clear.
Actual Result:
Changing "Purchase bill date" clears "Purchase bill status" Authorised value. I'm unable to set any value for the field.
NOTE : We are not sure it is intended
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6483020_1715886859158.bandicam_2024-05-16_21-03-00-340.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: