Repository navigation
Description
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.1.76-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @cead22
Slack conversation (hyperlinked to channel name): #Expensify bugs
Action Performed:
- Click workspaces > new workspace > enter name and confirm
- Go to workspace editor for that workspace > Reports > Switch on Report fields
- Click add field > press name and add a name > press type and select text > don't set an initial value > press save
- Create a report on that workspace
Expected Result:
Violation shows on the report fields
Actual Result:
no violation shows on the report fields in New Dot. If you load the report in Old Dot you should see a violation
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Recording.1379.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021941183565821524059
- Upwork Job ID: 1941183565821524059
- Last Price Increase: 2025-07-04
- Automatic offers:
- Tony-MK | Contributor | 108009026
Issue Owner
Current Issue Owner: @trjExpensifyMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone

Activity
melvin-bot commentedon Jul 4, 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 Jul 4, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021941183565821524059
[-]Report field violations aren't showing on reports page[/-][+][$250] Report field violations aren't showing on reports page[/+]melvin-bot commentedon Jul 4, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (
External)trjExpensify commentedon Jul 4, 2025
Dunno if this will really be FE-only, but we'll see.
Tony-MK commentedon Jul 4, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Report field violations aren't showing on the reports page.
What is the root cause of that problem?
The front end and the back end are not validating and merging the
fieldRequiredviolation.What changes do you think we should make in order to solve the problem?
In
ViolationUtils.getViolationsOnyxData, check if the transaction's report field is an empty value, and add thefieldRequiredviolation. We should create a property in thePolicyReportField, such asrequired, to check whether the violation should be added inViolationUtils.getViolationsOnyxData.What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
Create tests to check if the report field violations are being pushed optimistically to the onyx.
What alternative solutions did you explore? (Optional)
N/A
melvin-bot commentedon Jul 8, 2025
@rushatgabhane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
53 remaining items
melvin-bot commentedon Sep 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.8-4 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-09-17. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Sep 10, 2025
@rushatgabhane @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]
trjExpensify commentedon Sep 17, 2025
👋 checklist time here @rushatgabhane!
rushatgabhane commentedon Sep 19, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: N.A. frontend backend mismatch issue
[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: Not critical
[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.
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
Precondition:
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Sep 22, 2025
@trjExpensify Eep! 4 days overdue now. Issues have feelings too...
trjExpensify commentedon Sep 23, 2025
Payment summary as follows:
All set, closing!
garrettmknight commentedon Sep 30, 2025
$250 approved for @rushatgabhane