Skip to content

[Due for payment 2025-12-05] Expense - No category checkbox is shown when category cannot be set for IOU expense #76079

Closed

Description

@mitarachim

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.64-0
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: #72943
Email or phone of affected tester (no customers): onisdjoisjdosjdiojsd@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to 1:1 DM.
  3. Create two expenses.
  4. Open expense report.

Expected Result:

No category checkbox should be hidden because we cannot select category for IOU expense.

Actual Result:

No category checkbox is shown when we cannot select category for IOU expense.

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

Bug7013675_1764122648390.1.1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 26, 2025
  2. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (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 Nov 26, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 26, 2025

    @melvin-bot

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

  5. github-actions commented on Nov 26, 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. IuliiaHerets commented on Nov 26, 2025

    @IuliiaHerets

    Issue is not reproduced anymore

    20251126_181412.mp4
  7. JmillsExpensify commented on Nov 26, 2025

    @JmillsExpensify
    Contributor

    IOU issues are not a deploy blocker in my opinion.

  8. 20 remaining items

  9. changed the title [-]Expense - No category checkbox is shown when category cannot be set for IOU expense[/-] [+][Due for payment 2025-12-05] Expense - No category checkbox is shown when category cannot be set for IOU expense[/+] on Nov 28, 2025
  10. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.65-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-12-05. 🎊

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

    • @shubham1206agra requires payment through NewDot Manual Requests
    • @TaduJR requires payment (Needs manual offer from BZ)
  11. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    @shubham1206agra @mallenexpensify 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. trjExpensify commented on Dec 1, 2025

    @trjExpensify
    Contributor

    Can we close this, as it was taken care of in the PR for the report layout?

  13. mallenexpensify commented on Dec 3, 2025

    @mallenexpensify
    Contributor

    @shubham1206agra

    1. Is anyone due compensation here? It looks like this might be part of a project.
    2. This appears to be a regression, should we denote that on a parent issue to deduct 50%? The PR looks like it was a bit of a beast.
    Image
  14. melvin-bot commented on Dec 5, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (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
  15. mallenexpensify commented on Dec 6, 2025

    @mallenexpensify
    Contributor

    @shubham1206agra 👀 above plz

  16. shubham1206agra commented on Dec 6, 2025

    @shubham1206agra
    Contributor

    @mallenexpensify We will take care of payment in original issue.

  17. mallenexpensify commented on Dec 8, 2025

    @mallenexpensify
    Contributor

    Thanks @shubham1206agra , if test cases need to be created, plz do so as poart of the original issue.

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

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions