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
[HOLD for payment 2024-12-05] [Workspace feeds] When accounting integration is connected, there's no default in the card export row. It should be "Default card" #51891
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:
When accounting integration is connected, there's default card in the card export row.
Actual Result:
When accounting integration is connected, there's no default card in the card export row.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/-][+][Workspace feed] When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/+]on Nov 1, 2024
changed the title [-][Workspace feed] When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/-][+][Workspace feeds] When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/+]on Nov 4, 2024
@DylanDylann@twisterdotcom@DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
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 both staging and production
2d. 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: No because this seems like a case wasn't considered in document
[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
Test:
Choose the workspace from settings
Click company cards >Card Details
Verify that default export account is presented in Export row - with name "Default card"
Click on menu item - Verify that "Default card" is pre-selected -> choose other export account
Verify that selected export account presented in menu item row
Activity
melvin-bot commentedon Nov 1, 2024
Triggered auto assignment to @twisterdotcom (
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.
[-]When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/-][+][Workspace feed] When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/+][-][Workspace feed] When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/-][+][Workspace feeds] When accounting integration is connected, there's no default in the card export row. It should be "Default card"[/+]38 remaining items
melvin-bot commentedon Nov 28, 2024
@DylanDylann @twisterdotcom @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
mountiny commentedon Nov 29, 2024
@DylanDylann can you please add a checklist?
DylanDylann commentedon Dec 1, 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: No because this seems like a case wasn't considered in document
[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
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Dec 5, 2024
Payment Summary
Upwork Job
BugZero Checklist (@twisterdotcom)
twisterdotcom commentedon Dec 6, 2024
Payment Summary:
DylanDylann commentedon Dec 6, 2024
No need payment here, we will handle payment later
twisterdotcom commentedon Dec 9, 2024
Cool, withdrew the one sent above.