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-10-21] [CFI] Add coloured labels to report statuses in New Expensify #71549
Please re-state the problem that we are trying to solve in this issue.
The status of a NewDot report can sometimes be lost in the header, making it difficult for users to quickly identify the current state of their expense reports. Unlike OldDot which had colored labels to signify different report statuses, NewDot currently only displays status text without visual color coding, reducing the visual prominence and quick recognition of report states.
What is the root cause of that problem?
The root cause is that NewDot's current status display implementation only shows status text without any visual color differentiation. Currently:
Status text is displayed but not visually prominent: The getReportStatusTranslation function in ReportUtils returns plain text statuses like "Draft", "Outstanding", "Approved", "Paid", and "Done" without any color coding.
Status is currently shown in components like AvatarWithDisplayName, ParentNavigationSubtitle, and MoneyRequestReportPreviewContent as plain text without color differentiation.
What changes do you think we should make in order to solve the problem?
Create a new ReportStatusBadge component that displays status text with appropriate background colors:
Use the existing Badge component as a foundation (or can create new component for Icon-Based Status Indicators)
Map each report status to appropriate theme colors
Extend the existing badge color system in StyleUtils.getBadgeColorStyle() to support report status colors:
Add new badge style variants for each report status
Ensure proper contrast and accessibility in both light and dark themes
Update status display locations to use the new colored badge:
Modify AvatarWithDisplayName component to render ReportStatusBadge instead of plain text when shouldDisplayStatus is true
Update ParentNavigationSubtitle to use the colored badge for status display
Enhance MoneyRequestReportPreviewContent to show colored status badges
Add a utility function getReportStatusBadgeProps() in ReportUtils.ts:
Maps stateNum and statusNum combinations to appropriate badge colors and styles
Returns props that can be passed directly to the ReportStatusBadge component
Maintains consistency across all status display locations
Ensure responsive design: Make the badge size and positioning work well across different screen sizes and layouts.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
NA
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Activity
melvin-bot commentedon Sep 30, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (
External)miljakljajic commentedon Sep 30, 2025
cc @shawnborton
lorretheboy commentedon Sep 30, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
The status of a NewDot report can sometimes be lost in the header, making it difficult for users to quickly identify the current state of their expense reports. Unlike OldDot which had colored labels to signify different report statuses, NewDot currently only displays status text without visual color coding, reducing the visual prominence and quick recognition of report states.
What is the root cause of that problem?
The root cause is that NewDot's current status display implementation only shows status text without any visual color differentiation. Currently:
ReportUtilsreturns plain text statuses like "Draft", "Outstanding", "Approved", "Paid", and "Done" without any color coding.App/src/libs/ReportUtils.ts
Line 11774 in 61dbac2
Status is currently shown in components like
AvatarWithDisplayName,ParentNavigationSubtitle, andMoneyRequestReportPreviewContentas plain text without color differentiation.What changes do you think we should make in order to solve the problem?
StyleUtils.getBadgeColorStyle()to support report status colors:AvatarWithDisplayNamecomponent to renderReportStatusBadgeinstead of plain text whenshouldDisplayStatusis trueParentNavigationSubtitleto use the colored badge for status displayMoneyRequestReportPreviewContentto show colored status badges...etc
App/src/components/ParentNavigationSubtitle.tsx
Line 115 in ca5897a
App/src/components/ReportActionItem/MoneyRequestReportPreview/MoneyRequestReportPreviewContent.tsx
Line 682 in 9d59d10
App/src/components/AvatarWithDisplayName.tsx
Line 282 in d3dcb0d
getReportStatusBadgeProps()in ReportUtils.ts:What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
NA
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
samranahm commentedon Sep 30, 2025
@miljakljajic The images are not loading in OP
miljakljajic commentedon Sep 30, 2025
Reposting!
miljakljajic commentedon Sep 30, 2025
Should be all good now.
melvin-bot commentedon Sep 30, 2025
Triggered auto assignment to @sonialiap (
NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO. Remember to draft any necessary HelpDot updates by following the instructions here.30 remaining items
sonialiap commentedon Oct 21, 2025
Payment summary:
@suneox $250 please request in NewDot and propose a regression test
@lorretheboy $250 offer sent in upwork - paid
suneox commentedon Oct 27, 2025
We still have a PR fixing the regression issue that’s waiting to be merged
suneox commentedon Oct 27, 2025
Regression Test Proposal
Precondition: Prepare reports with different statuses
Do we agree 👍 or 👎
melvin-bot commentedon Oct 28, 2025
@sonialiap Whoops! This issue is 2 days overdue. Let's get this updated quick!
sonialiap commentedon Oct 29, 2025
Thanks!
melvin-bot commentedon Nov 1, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
garrettmknight commentedon Nov 21, 2025
$250 approved for @suneox