Skip to content

Expense - System message for amount edit is shown when the amount is saved without edit #71012

Closed

Description

@lanitochka17

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.2.15-1 PR:65001
Reproducible in staging?: N
Reproducible in production?: N
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): jsdoinjosdjosjniosdj@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to 65001.pr-testing.expensify.com
  2. Go to workspace chat
  3. Create an expense with negative amount
  4. Open the transaction thread
  5. Click Report
  6. Click Remove from report
  7. Go to self DM
  8. Open the unreported expense
  9. Click Amount
  10. Without editing the amount, click Save

Expected Result:

There will be no system message for amount edit since the amount is saved without edit

Actual Result:

System message for amount edit is shown when the amount is saved without edit

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6952495_1758559874085.Screen_Recording_2025-09-23_at_00.49.09.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @pasyukevich

Activity

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

    @melvin-bot

    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.

  3. github-actions commented on Sep 22, 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.
  4. melvin-bot commented on Sep 22, 2025

    @melvin-bot

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

  5. melvin-bot commented on Sep 22, 2025

    @melvin-bot

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

  6. luacmartins commented on Sep 22, 2025

    @luacmartins
    Contributor

    @lanitochka17 is this a deploy blocker? The test steps mention using 65001.pr-testing.expensify.com as the test base. That PR is not merged yet.

  7. luacmartins commented on Sep 22, 2025

    @luacmartins
    Contributor

    Not reproducible in staging, this flow doesn't exist there.

  8. 8 remaining items

  9. luacmartins commented on Oct 6, 2025

    @luacmartins
    Contributor

    This is being worked on in the original PR

  10. melvin-bot commented on Oct 9, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  11. pasyukevich commented on Oct 10, 2025

    @pasyukevich
    Contributor

    The original PR has been merged - the issue is not reproducible on stage

    Screen.Recording.2025-10-10.at.17.40.47.mov
  12. melvin-bot commented on Oct 13, 2025

    @melvin-bot

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

  13. melvin-bot commented on Oct 13, 2025

    @melvin-bot

    @pasyukevich Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  14. luacmartins commented on Oct 13, 2025

    @luacmartins
    Contributor

    Closing since the issue is no longer reproducible and this was a regression.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions