-
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
[QBO] "must categorize all expenses" toggle is off and Tags are not imported #41844
Comments
Triggered auto assignment to @jliexpensify ( |
Triggered auto assignment to @youssef-lr ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@jliexpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think this issue might be related to the #collect project. |
cc @hayata-suenaga @aldo-expensify, is this a blocker? taking a look at the code it seems expected here that the toggle will be disable if we're connected to an accounting system
|
I think the QBO stuff is behind a beta, no? Let's remove the blocker. |
The bug is partly fixed. The toggle part is still repro ('Members must categorize all spend' toggle still off and locked) 41513.v2.mp4 |
On Tags import:
As for the required categories toggle, I can't repro that: |
@aldo-expensify, could you confirm that, in this issue, you accounted for the situation when the default configuration already satisfies the condition below:
|
For the bug (somewhat unrelated) I found while reproducing the original issue, the issue is apparently hard to reproduce. It might have been the result of the backend fire this week. Please let me know if you encounter this issue (Not found page briefly displayed after a while) again. |
ohh, I think initial case was not covered because I added that logic to the Auth command I think we can fix this here: https://github.com/Expensify/Web-Expensify/pull/41908 |
Ignore this, I had a problem in dev that caused the defaults to fail to be set. We do enable Classes. Customer/Projects and Locations to be imported by default. |
Just to confirm on this.. in OldDot, we enable |
Also, nice! Looking forward to getting that one fixed 👍 |
Yes, I made a mistake, |
Sounds good! |
@youssef-lr, @jliexpensify Eep! 4 days overdue now. Issues have feelings too... |
Not overude. A fix has been merged |
Looks like this was deployed, @youssef-lr should we close this, or did you want Applause to re-test? |
@jliexpensify it's only been deployed to staging, we can close once it hits production. |
Ah yes, you're correct - apologies! |
@youssef-lr @jliexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
This one just hit production, so closing it out! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.71-4
Reproducible in staging?: Y
Reproducible in production?: Unable to check
Found when validating PR : #41513
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition: Log into New Expensify using an account that is on the accounting beta list
Expected Result:
Step 7. "must categorize all expenses" toggle is on
Step 8. Customers (or locations or classes) are imported as tags
Step 9. You see some tags (you should not see the tag you created before)
Actual Result:
Step 7. "must categorize all expenses" toggle is off and locked
Step 8. Customers (or locations or classes) are Not imported
Step 9. You see the tag you created on step 4
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6474708_1715166353268.41513.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: