Repository navigation
[HOLD for payment 2025-02-07] [HOLD for payment 2025-02-05] We aren't showing broken connection error on the feed when the connection is broken #55103
Description
Activity
- addedDailyKSv2KSv2Needs ReproductionReproducible steps neededReproducible steps neededBugSomething is broken. Auto assigns a BugZero manager.Something is broken. Auto assigns a BugZero manager.
on Jan 10, 2025 Triggered auto assignment to @alexpensify (
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.This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
please assign me here, callstack will implement this one most probably
- removedNeeds ReproductionReproducible steps neededReproducible steps needed
on Jan 12, 2025 Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.
22 remaining items
- changed the title
[-][HOLD for payment 2025-02-05] We aren't showing broken connection error on the feed when the connection is broken[/-][+][HOLD for payment 2025-02-07] [HOLD for payment 2025-02-05] We aren't showing broken connection error on the feed when the connection is broken[/+]on Jan 31, 2025 The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.92-6 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-02-07. 🎊
For reference, here are some details about the assignees on this issue:
- @VickyStash does not require payment (Contractor)
- @getusha requires payment through NewDot Manual Requests
@getusha @alexpensify @getusha 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]
Payment Summary
- Contributor: @VickyStash is from an agency-contributor and not due payment
- Reviewer: @getusha owed $250 via NewDot
BugZero Checklist (@alexpensify)
- I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
- I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
- I have paid out the Upwork contracts or cancelled the ones that are incorrect
- I have verified the payment summary above is correct
@alexpensify, @VickyStash, @mountiny, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick!
Contributor: @VickyStash agency-contributor and not due payment
Contributor+: @getusha owed $250 via NewDotPlease submit a request in Chat. Thanks!
- moved this from MEDIUM to Done in [wave-collect] Workspace Feeds
on Feb 8, 2025 $250 approved for @getusha
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
- StatusShow more project fieldsDone
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
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): convert
Action Performed:
Expected Result:
Broken connection error on the card feed page
Actual Result:
No error message displayed in feed page. Only thing that indicates it is not working properly is, no cards left to assign message displayed (when there is one left)
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @alexpensify