Skip to content

[Due for payment 2025-03-27] Track expense - Unable to delete track expense from context menu #58571

Closed

Description

@jponikarchuk

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: 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.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Track a manual expense.
  4. Right click on the expense preview.
  5. 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.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6773280_1742230933533.delete.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 17, 2025
  2. melvin-bot commented on Mar 17, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Mar 17, 2025

    @melvin-bot

    Triggered auto assignment to @neil-marcellini (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Mar 17, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Mar 17, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. samranahm commented on Mar 17, 2025

    @samranahm
    Contributor

    🚨 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

    const reportID = isMoneyRequestAction(moneyRequestAction) ? getOriginalMessage(moneyRequestAction)?.IOUReportID : reportIDParam;

    when isMoneyRequestAction reportID becomes 0 leading to not displaying delete Model

    What changes do you think we should make in order to solve the problem?

    if (closePopover) {
    // Hide popover, then call showDeleteConfirmModal
    hideContextMenu(false, () => showDeleteModal(reportID, moneyRequestAction ?? reportAction));
    return;
    }
    // No popover to hide, call showDeleteConfirmModal immediately
    showDeleteModal(reportID, moneyRequestAction ?? reportAction);
    },

    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 showDeleteConfirmModal
            hideContextMenu(false, () => showDeleteModal(reportIDParam, moneyRequestAction ?? reportAction));
            return;
        }
    
        // No popover to hide, call showDeleteConfirmModal immediately
        showDeleteModal(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.

  7. github-actions commented on Mar 17, 2025

    @github-actions
    Contributor

    ⚠️ 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).

  8. 18 remaining items

  9. melvin-bot commented on Mar 27, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • ROLE: @daledah paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@JmillsExpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary 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
  10. JmillsExpensify commented on Mar 27, 2025

    @JmillsExpensify
    Contributor

    Payment summary: $250 to @daledah via Upwork.

  11. JmillsExpensify commented on Mar 27, 2025

    @JmillsExpensify
    Contributor

    Offer sent

  12. JmillsExpensify commented on Mar 29, 2025

    @JmillsExpensify
    Contributor

    All paid out.

  13. rushatgabhane commented on Apr 2, 2025

    @rushatgabhane
    Member

    @JmillsExpensify requesting payment summary for review of PR, thank you!
    #58590 (comment)

  14. garrettmknight commented on Apr 10, 2025

    @garrettmknight
    Contributor

    @JmillsExpensify can you confirm if @rushatgabhane should get payment here and update the summary if that's the case?

  15. melvin-bot commented on Apr 14, 2025

    @melvin-bot

    @JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  16. JmillsExpensify commented on Apr 16, 2025

    @JmillsExpensify
    Contributor

    Payment summary for @rushatgabhane: $250 for PR review and testing.

  17. garrettmknight commented on Apr 22, 2025

    @garrettmknight
    Contributor

    $250 approved for @rushatgabhane

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions