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-03] [Company cards] Navigate to some other existing feed after removing one #52886
When user has 2 or more company card feeds and we remove one of them, make sure to navigate them and show them some other feed right after the removal. No particular order, just take the first one in the domain_member object
Issue is ready for payment but no BZ is assigned. @bfitzexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
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:
[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.
[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:
Create a workspace.
Enable Company cards feature.
Add at least two feeds to the workspace.
Open one of the created feeds. Go to Settings and Remove it. Make sure another feed will be opened for you.
Remove the second feed as well. Make sure you see the no feed view.
Activity
melvin-bot commentedon Nov 21, 2024
Triggered auto assignment to @OfstadC (
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.mountiny commentedon Nov 21, 2024
No need for b0
VickyStash commentedon Nov 21, 2024
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.
14 remaining items
melvin-bot commentedon Dec 3, 2024
Issue is ready for payment but no BZ is assigned. @bfitzexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
melvin-bot commentedon Dec 3, 2024
Payment Summary
Upwork Job
BugZero Checklist (@bfitzexpensify)
DylanDylann commentedon Dec 3, 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:
[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: https://expensify.slack.com/archives/C06ML6X0W9L/p1732116549221049?thread_ts=1732108983.281759&cid=C06ML6X0W9L
[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 👎
mountiny commentedon Dec 3, 2024
@DylanDylann can you please add comments or link prs in all the checklist sections?
DylanDylann commentedon Dec 3, 2024
@mountiny
About this point, this is not a bug, when implementing this feature we already missed from the design doc
mountiny commentedon Dec 3, 2024
Ok, nice feel free to leave such quick note in the checklist in future
mountiny commentedon Dec 3, 2024
@bfitzexpensify lets please add this regression test
bfitzexpensify commentedon Dec 3, 2024
Regression steps proposed. @DylanDylann offer sent for payment.
DylanDylann commentedon Dec 4, 2024
No need payment here. Let's close this issue