-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-05-14] [Due for payment 2025-05-08] Reports -"Complete" button on deleted task becomes responsive when turning to Most Recent mode #61025
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Triggered auto assignment to @Beamanator ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Complete" button on deleted task becomes responsive when turning to Most Recent mode What is the root cause of that problem?Here App/src/components/SelectionList/Search/TaskListItemRow.tsx Lines 103 to 105 in bd0f3f2
we check if the complete button should be disable inside Lines 1238 to 1240 in bd0f3f2
Then inside Lines 1314 to 1318 in bd0f3f2
When we delete the task report What changes do you think we should make in order to solve the problem?We should explicitly check is the report is closed here then return true if (!isEmptyObject(report) && (report?.isDeletedParentAction || isClosedReport(report))) {
return true;
} What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?N/A What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
@samranahm thanks so much for the proposal! But since this is a deploy blocker, we're pretty confident this bug came from a recent PR, so we would like to prioritize finding which PR caused this bug so the PR author can fix this... Can you help us find the PR that may have caused this bug? 🙏 |
@Beamanator Is this a new feature? #59672 |
@Beamanator Seems like this blocker is related to #59672 and this commit but this commit only pass so we should keep it separated |
Great catches, y'all! Will discuss with @JS00001 👍 |
This PR was reverted and is now off of staging |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.38-4 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-05-08. 🎊 |
@Beamanator / @JS00001 @laurenreidexpensify @Beamanator / @JS00001 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] |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.40-7 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-05-14. 🎊 |
@Beamanator / @JS00001 @laurenreidexpensify @Beamanator / @JS00001 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] |
Doesnt need payment, this was fixed internally |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.1.33-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Other
Action Performed:
Expected Result:
Deleted task shouldn´t display the option to be marked as complete.
Actual Result:
"Complete" button on deleted task on "Reports" becomes responsive again after switching to "Focus" mode and returning to "Most Recent". Tapping on it, triggers a "You don´t have permission to take the requested action" error message and after this action, a new chat for the task, appears on LHN, with a RBR that can´t be dismissed.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6815835_1745888722617.Recent.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @laurenreidexpensifyThe text was updated successfully, but these errors were encountered: