You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-12-26] Reports - Date width does not auto adjust after updating expense date, date is out of view #77868
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:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Reports > Expenses.
Click on the expense.
Change the date to 2024 and save it.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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:
@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]
Activity
melvin-bot commentedon Dec 17, 2025
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.melvin-bot commentedon Dec 17, 2025
Triggered auto assignment to @NikkiWines (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 17, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 17, 2025
👋 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:
m-natarajan commentedon Dec 17, 2025
Windows 10 / Chrome
v9.2.81-0 PR:77837
Issue not reproducible
Repro77868Web.mp4
IuliiaHerets commentedon Dec 18, 2025
Not reproducible with v9.2.81-4
77868w.mp4
luacmartins commentedon Dec 18, 2025
Fixed
[-]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[/+]melvin-bot commentedon Dec 19, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 19, 2025
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. 🎊
melvin-bot commentedon Dec 19, 2025
@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]