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
[Due for payment 2025-03-27] Track expense - Unable to delete track expense from context menu #58571
Version Number: 9.1.14-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):jsdsjdojsdoijo@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Account has self DM.
Go to staging.new.expensify.com
Go to self DM.
Track a manual expense.
Right click on the expense preview.
Click Delete expense.
Expected Result:
There will be a delete modal when deleting expense from context menu.
Actual Result:
There is no delete modal when deleting expense from context menu.
👋 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:
Identify the pull request that introduced this issue and revert it.
Here we are getting report ID from original message but we should pass the report Id from reportIDParam
onPress: (closePopover,{reportID: reportIDParam, reportAction, moneyRequestAction})=>{if(closePopover){// Hide popover, then call showDeleteConfirmModalhideContextMenu(false,()=>showDeleteModal(reportIDParam,moneyRequestAction??reportAction));return;}// No popover to hide, call showDeleteConfirmModal immediatelyshowDeleteModal(reportIDParam,moneyRequestAction??reportAction);},
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
What alternative solutions did you explore? (Optional)
N/A 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.
⚠️ Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).
Activity
melvin-bot commentedon Mar 17, 2025
Triggered auto assignment to @JmillsExpensify (
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 Mar 17, 2025
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 17, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 17, 2025
👋 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:
samranahm commentedon Mar 17, 2025
🚨 Edited by proposal-police: This proposal was edited at 2025-03-17 17:56:14 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
Track expense - Unable to delete track expense from context menu
What is the root cause of that problem?
here
App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx
Line 769 in 9dc9fb1
when
isMoneyRequestActionreportID becomes 0 leading to not displaying delete ModelWhat changes do you think we should make in order to solve the problem?
App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx
Lines 770 to 778 in fa8eb81
Here we are getting report ID from original message but we should pass the report Id from reportIDParam
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
What alternative solutions did you explore? (Optional)
N/A
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.
github-actions commentedon Mar 17, 2025
18 remaining items
melvin-bot commentedon Mar 27, 2025
Payment Summary
Upwork Job
BugZero Checklist (@JmillsExpensify)
JmillsExpensify commentedon Mar 27, 2025
Payment summary: $250 to @daledah via Upwork.
JmillsExpensify commentedon Mar 27, 2025
Offer sent
JmillsExpensify commentedon Mar 29, 2025
All paid out.
rushatgabhane commentedon Apr 2, 2025
@JmillsExpensify requesting payment summary for review of PR, thank you!
#58590 (comment)
garrettmknight commentedon Apr 10, 2025
@JmillsExpensify can you confirm if @rushatgabhane should get payment here and update the summary if that's the case?
melvin-bot commentedon Apr 14, 2025
@JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
JmillsExpensify commentedon Apr 16, 2025
Payment summary for @rushatgabhane: $250 for PR review and testing.
garrettmknight commentedon Apr 22, 2025
$250 approved for @rushatgabhane