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
{{ message }}
Repository navigation
[Workspace feeds] We're erroneously showing an export row when "vendor bill" is selected as the export option for QBO #51887
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs reproduction If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: 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:@joekaufmanexpensify Slack conversation (hyperlinked to channel name): #quality
Action Performed:
Prerequisite:
Members and company cards added in workspace
Go to staging.new.expensify.com
Choose the workspace from settings
Click company cards >Card Details
Expected Result:
No export row if Vendor bill is selected as the export option for QBO
Actual Result:
Export row displayed for QBO option and clicking it results in No accounts found page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence

changed the title [-]We're erroneously showing an export row when "vendor bill" is selected as the export option for QBO[/-][+][Workspace feed] We're erroneously showing an export row when "vendor bill" is selected as the export option for QBO[/+]on Nov 1, 2024
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production
2b. Reported on staging (deploy blocker)
2c. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I think we don't need to comment on the previous PR because @narefyev91 also be author of this feature
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Prerequisite
Members and company cards added in workspace
Test:
Choose the workspace from settings
Click company cards >Card Details
Verify that default export account is presented in Export row
Go to Accounting > Export > Export company card expenses as > Export as. And update to Vendor Bill
We will handle the regression testing with Joe as part of the project and payments will be all done together for the project so I think we can close this now
Activity
melvin-bot commentedon Nov 1, 2024
Triggered auto assignment to @sakluger (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.m-natarajan commentedon Nov 1, 2024
BZ team member, Callstack will work on this issue, please wait for them to comment before moving the issue forward.
MelvinBot commentedon Nov 1, 2024
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
melvin-bot commentedon Nov 1, 2024
Current assignee @mountiny is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new.
[-]We're erroneously showing an export row when "vendor bill" is selected as the export option for QBO[/-][+][Workspace feed] We're erroneously showing an export row when "vendor bill" is selected as the export option for QBO[/+]narefyev91 commentedon Nov 4, 2024
Hi, I'm Nicolay from Callstack - expert contributor group - and I would like to work on this issue.
1 remaining item
DylanDylann commentedon Nov 20, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I think we don't need to comment on the previous PR because @narefyev91 also be author of this feature
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Prerequisite
Members and company cards added in workspace
Test:
Do we agree 👍 or 👎
DylanDylann commentedon Nov 20, 2024
@sakluger Could you help to assign me to this issue? Because I already reviewed the PR
Small note: PR was deployed to prod on 11/13
mountiny commentedon Nov 20, 2024
We will handle the regression testing with Joe as part of the project and payments will be all done together for the project so I think we can close this now