Skip to content

[Due for payment 2025-06-02] [$250] Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id #61573

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: V9.1.41-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6064918
Email or phone of affected tester (no customers): Slottwo1 sivappa2@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote note 10s android 13
App Component: Money Requests

Action Performed:

  1. Launch app
  2. Login with expensifail account
  3. Tap fab and create a new workspace
  4. Tap fab - create expense
  5. Enter amount and tap next
  6. Note report field shows expense report 2025-05-07
  7. Tap create expense entering merchant
  8. Open the expense
  9. Note header and report section

Expected Result:

Both in confirmation page and after creating expense report field must show same details.

Actual Result:

Expense confirmation page shows report as expense report 2025-05-07 but on opening created expense it disappears in a brief time and header & report displays as expense report #7533444478.

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

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021920643087475662947
  • Upwork Job ID: 1920643087475662947
  • Last Price Increase: 2025-05-16
  • Automatic offers:
    • nkdengineer | Contributor | 107359669
Issue OwnerCurrent Issue Owner: @jliexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 7, 2025
  2. melvin-bot commented on May 7, 2025

    @melvin-bot

    Triggered auto assignment to @kadiealexander (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. kadiealexander commented on May 8, 2025

    @kadiealexander
    Contributor

    Android <> iOS bug swap

  4. jliexpensify commented on May 8, 2025

    @jliexpensify
    Contributor

    @jponikarchuk Can you confirm if this behaviour is reproducible with a normal account? Expensifail is an internal testing account so if it can't be reproduced on a standard account, we can probably close this.

    Also the tester email is sivappa2@gmail.com - what Expensifail account were they using?

  5. jponikarchuk commented on May 8, 2025

    @jponikarchuk
    Author

    @jliexpensify Report field is not available for Gmail user in expense. We can test this with Expensify account only.

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 9, 2025
  7. changed the title [-]Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id[/-] [+][$250] Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id[/+] on May 9, 2025
  8. melvin-bot commented on May 9, 2025

    @melvin-bot
  9. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 9, 2025
  10. 36 remaining items

  11. melvin-bot commented on May 26, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 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-06-02. 🎊

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

  12. melvin-bot commented on May 26, 2025

    @melvin-bot

    @dukenv0307 @jliexpensify @dukenv0307 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]

  13. dukenv0307 commented on May 27, 2025

    @dukenv0307
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/47468/files#r2108110847

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. Yes

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Go offline
    2. Create new WS
    3. Open WS report page
    4. Verify that the default report title is shown
    5. Create expense with this WS
    6. Verify the report name is displayed

    Do we agree 👍 or 👎

  14. jliexpensify commented on Jun 3, 2025

    @jliexpensify
    Contributor

    Sorting out payment today

  15. jliexpensify commented on Jun 6, 2025

    @jliexpensify
    Contributor

    UGH I am sorry! I totally missed this the other day. Sorting it out now for real!

  16. jliexpensify commented on Jun 6, 2025

    @jliexpensify
    Contributor

    Payment Summary

  17. jliexpensify commented on Jun 6, 2025

    @jliexpensify
    Contributor

    Paid and job closed

  18. quinthar commented on Sep 17, 2025

    @quinthar
    Contributor

    $250 approved to @dukenv0307

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions