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 2025-01-28] [Workspace Feeds] Adding additional custom feed overwrites the existing feed #52002
Version Number: Reproducible in staging?: need reproduction Reproducible in production?: need 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:
Set up a Visa feed
Add additional Visa feed with existing one
Expected Result:
2nd Visa card should be showing as pending
Actual Result:
Existing already added visa card is overwritten
NOTE : Issue not happening with different types of card feed
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 evidence2024-11-04_16-00-46.2.mp4
changed the title [-]Adding additional feed overwrites the existing feed[/-][+][Workspace Feeds] Adding additional feed overwrites the existing feed[/+]on Nov 4, 2024
changed the title [-][Workspace Feeds] Adding additional custom feed overwrites the existing feed[/-][+][HOLD for payment 2025-01-28] [Workspace Feeds] Adding additional custom feed overwrites the existing feed[/+]on Jan 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.87-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@mountiny@garrettmknight@mountiny 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]
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
melvin-bot commentedon Nov 4, 2024
Triggered auto assignment to @garrettmknight (
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.melvin-bot commentedon Nov 4, 2024
Current assignee @mountiny is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new.
[-]Adding additional feed overwrites the existing feed[/-][+][Workspace Feeds] Adding additional feed overwrites the existing feed[/+]mountiny commentedon Nov 4, 2024
I think we might need to pass updated name like
vcf2m-natarajan commentedon Nov 4, 2024
BZ team member, Callstack will work on this issue, please wait for them to comment before moving the issue forward.
22 remaining items
[-][Workspace Feeds] Adding additional custom feed overwrites the existing feed[/-][+][HOLD for payment 2025-01-28] [Workspace Feeds] Adding additional custom feed overwrites the existing feed[/+]melvin-bot commentedon Jan 21, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.87-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-01-28. 🎊
melvin-bot commentedon Jan 21, 2025
@mountiny @garrettmknight @mountiny 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]
melvin-bot commentedon Jan 28, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
melvin-bot commentedon Mar 7, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.