-
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
Xero - Export button is showing in report details page for Admin, but not for Employee #45590
Comments
Triggered auto assignment to @rlinoz ( |
Triggered auto assignment to @zanyrenney ( |
👋 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:
|
We think this issue might be related to the #collect project. |
I'm not sure, but this PR might fix it: #45577 |
I think it's expected that we only show export button with admin or manager. |
Exactly. We should only show the export button if it's an admin or manager. Currently we're showing the export option for both (Admin/Manager and Member) if we're in a QBO setup which is wrong. My PR #45577 solves that so it only shows the export to integration button if it's an Admin/Manager, just like the backend expects it. |
Cool, so we can close this one as working as expected. |
Moving over to the PR for that Q. 👀 |
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: 9.0.8-1
Reproducible in staging?: Y
Reproducible in production?: New feature
Found when validating PR : #44170
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:
Expected Result:
There should be consistency in showing Export button in report details page for both admin and employee.
Actual Result:
Export button is showing in report details page for Admin, but not for Employee.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6544826_1721203779570.20240717_160308.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: