Skip to content

[Due for payment 2025-12-26] Reports - Date width does not auto adjust after updating expense date, date is out of view #77868

Closed

Description

@nlemma

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.79-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: #77673
Email or phone of affected tester (no customers): sdsjdoisjoinjoijsoijsd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Reports > Expenses.
  5. Click on the expense.
  6. Change the date to 2024 and save it.
  7. Close the expense report.

Expected Result:

Date width will auto adjust so that the entire date will fit in the column.

Actual Result:

Date width does not auto adjust after updating expense date. Date year is out of view.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7031872_1765960871724.16.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @trjExpensify (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 Dec 17, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 17, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 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. m-natarajan commented on Dec 17, 2025

    @m-natarajan

    Windows 10 / Chrome
    v9.2.81-0 PR:77837
    Issue not reproducible

    Repro77868Web.mp4
  7. IuliiaHerets commented on Dec 18, 2025

    @IuliiaHerets

    Not reproducible with v9.2.81-4

    77868w.mp4
  8. luacmartins commented on Dec 18, 2025

    @luacmartins
    Contributor

    Fixed

  9. linked a pull request that will close this issueFix custom columns blocker #2 #77888on Dec 19, 2025
  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 19, 2025
  11. changed the title [-]Reports - Date width does not auto adjust after updating expense date, date is out of view[/-] [+][Due for payment 2025-12-26] Reports - Date width does not auto adjust after updating expense date, date is out of view[/+] on Dec 19, 2025
  12. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  13. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.84-8 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-26. 🎊

  14. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    @luacmartins / @JS00001 @trjExpensify 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]

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.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions