You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go to More Features > Tags > Enable (you need this step for now because otherwise Tags won't show in the LHN after you connect to QBO to see the imported coding, apparently that's going to be worked on here)
Enable Accounting in More Features as well
Go to Accounting in the workspace settings LHN
Connect to QBO
Go to Categories
Select a couple of category in the table
Click the [2 selected v] button in the page header
Observe the Delete categories button that shouldn't be there
Close the RHP modal
Click on a category in the table
Observe the three dot overflow menu in the category settings page in the RHP that shouldn't be there
Click the overflow menu
Observe the Delete category menu item that shouldn't be there.
Close the modal
Go to the Tags page
Observe the Add tag button in the page header that shouldn't be there
Repeat steps 7-14 above and observe that the admin can also delete imported tag values
Expected Result:
When coding features (Categories, Tags, Taxes) are imported from QBO, you shouldn't be able to Add or Delete the imported values. As such:
The green Add X button should be hidden in the page header
The Delete X menu item should be hidden in the bulk selection menu, only Disable X || Enable X should be shown.
The overflow menu in the category setting page should be hidden as the only menu item within it is to Delete x which shouldn't be allowed
Note: Untested but likely true given the above so please check on dev, and make sure we apply the same fix to Taxes imported to the workspace as well.
Actual Result:
Admins can Add and Delete imported coding values when connected to QBO
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
N/A
Platforms:
Which of our officially supported platforms is this issue occurring on?
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: v1.4.68-0
Reproducible in staging?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1714438462878199?thread_ts=1714400674.229349&cid=C036QM0SLJK
Action Performed:
Tagswon't show in the LHN after you connect to QBO to see the imported coding, apparently that's going to be worked on here)Accountingin More Features as wellAccountingin the workspace settings LHN[2 selected v]button in the page headerDelete categoriesbutton that shouldn't be thereDelete categorymenu item that shouldn't be there.TagspageAdd tagbutton in the page header that shouldn't be thereExpected Result:
When coding features (
Categories,Tags,Taxes) are imported from QBO, you shouldn't be able toAddorDeletethe imported values. As such:Add Xbutton should be hidden in the page headerDelete Xmenu item should be hidden in the bulk selection menu, onlyDisable X||Enable Xshould be shown.Delete xwhich shouldn't be allowedNote: Untested but likely true given the above so please check on dev, and make sure we apply the same fix to
Taxesimported to the workspace as well.Actual Result:
Admins can
AddandDeleteimported coding values when connected to QBOWorkaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
N/A
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
2024-04-30_01-44-14.mp4
View all open jobs on GitHub