Skip to content

[Due for payment 2025-11-03] Reports - After reset app, expense row does not show negative sign on Reports > Expenses #72205

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.2.28-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #65001
Email or phone of affected tester (no customers): jsdoijnsondijodjnsoj@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense with negative amount in workspace chat.
  4. Go to Account > Troubleshoot > Clear cache and restart > Reset and refresh.
  5. Go to Reports > Expenses.

Expected Result:

After reset app, expense row will show the negative amount on Reports > Expenses.

Actual Result:

After reset app, expense row does not show the negative amount on Reports > Expenses. It appears as positive amount.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @greg-schroeder

Activity

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

    @melvin-bot

    Triggered auto assignment to @greg-schroeder (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 Oct 9, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 9, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 9, 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. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 9, 2025
  7. 29 remaining items

  8. changed the title [-]Reports - After reset app, expense row does not show negative sign on Reports > Expenses[/-] [+][Due for payment 2025-11-03] Reports - After reset app, expense row does not show negative sign on Reports > Expenses[/+] on Oct 27, 2025
  9. melvin-bot commented on Oct 27, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  10. melvin-bot commented on Oct 27, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.38-5 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-11-03. 🎊

    For reference, here are some details about the assignees on this issue:

  11. melvin-bot commented on Oct 27, 2025

    @melvin-bot

    @eh2077 @greg-schroeder 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]

  12. melvin-bot commented on Nov 3, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @pasyukevich is from an agency-contributor and not due payment
    • Contributor: @kubabutkiewicz is from an agency-contributor and not due payment
    • Contributor: @LukasMod is from an agency-contributor and not due payment
    • Reviewer: @eh2077 owed $250 via NewDot

    BugZero Checklist (@greg-schroeder)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • 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 verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. greg-schroeder commented on Nov 5, 2025

    @greg-schroeder
    Contributor

    Handling

  14. greg-schroeder commented on Nov 5, 2025

    @greg-schroeder
    Contributor

    Payment summary:

    Reviewer: @eh2077 - $250 - Manual request via ND

    Approved for the above ☝️

  15. garrettmknight commented on Nov 21, 2025

    @garrettmknight
    Contributor

    $250 approved for @eh2077

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