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
src/languages/en.ts (and all language files) - Add [CONST.SEARCH.GROUP_BY.TAG]: 'Tag' to search.filters.groupBy
Add "Tag" to Group Columns on Search Columns Page (follow the same pattern as existing group columns: FROM, CARD, WITHDRAWAL_ID, CATEGORY, MERCHANT)
Define the GROUP_TAG table column constant in the TABLE_COLUMNS object - src/CONST/index.ts
Add a TAG entry to GROUP_CUSTOM_COLUMNS to define which group columns are available when grouping by tag. Include tag, expenses, total - src/CONST/index.ts
Add a TAG entry to GROUP_DEFAULT_COLUMNS that specifies the default columns to show when grouping by tag - src/CONST/index.ts
Add a user friendly name mapping for the GROUP_TAG column - src/CONST/index.ts
Handle the TAG case in getCustomColumns() to return the tag custom columns - src/libs/SearchUIUtils.ts
Handle the TAG case in getCustomColumnDefault() to return the default tag columns - src/libs/SearchUIUtils.ts
Add TAG mappings to both the customColumns and defaultCustomColumns objects in getColumnsToShow() - src/libs/SearchUIUtils.ts
Add a conditional check in getColumnsToShow() to ensure required columns (AVATAR and GROUP_TAG) are always included when grouping by tag - src/libs/SearchUIUtils.ts
Add a case for GROUP_TAG in getSearchColumnTranslationKey() that returns the tag translation key - src/libs/SearchUIUtils.ts
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 Jan 23, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (
External)melvin-bot commentedon Jan 23, 2026
Triggered auto assignment to @CortneyOfstad (
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.melvin-bot commentedon Jan 23, 2026
Triggered auto assignment to Design team member for new feature review - @shawnborton (
NewFeature)PiyushChandra17 commentedon Jan 23, 2026
🚨 Edited by proposal-police: This proposal was edited at 2026-01-23 23:41:29 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
[Insights] [Release 3] Add group-by:tag
What is the root cause of that problem?
New Feature
What changes do you think we should make in order to solve the problem?
Reports>Expenses(group-by:tag)group-by:frominTop SpendersTAG: 'tag'toCONST.SEARCH.GROUP_BYApp/src/CONST/index.ts
Lines 6827 to 6831 in 9c1b8c3
App/src/languages/en.ts
Lines 6771 to 6775 in 9c1b8c3
Define the
GROUP_TAGtable column constant in theTABLE_COLUMNSobjectApp/src/CONST/index.ts
Lines 7012 to 7014 in 5b76720
Add a
TAGentry toGROUP_CUSTOM_COLUMNSto define which group columns are available when grouping by tag. Include tag, expenses, totalApp/src/CONST/index.ts
Lines 6858 to 6878 in 5b76720
Add a
TAGentry toGROUP_DEFAULT_COLUMNSthat specifies the default columns to show when grouping by tagApp/src/CONST/index.ts
Lines 6908 to 6919 in 5b76720
GROUP_TAGcolumnApp/src/CONST/index.ts
Lines 7180 to 7194 in 5b76720
TAGcase ingetCustomColumns()to return the tag custom columnsApp/src/libs/SearchUIUtils.ts
Lines 2578 to 2600 in 5b76720
TAGcase ingetCustomColumnDefault()to return the default tag columnsApp/src/libs/SearchUIUtils.ts
Lines 2603 to 2626 in 5b76720
TAGmappings to both thecustomColumnsanddefaultCustomColumnsobjects in getColumnsToShow()App/src/libs/SearchUIUtils.ts
Lines 3159 to 3170 in 5b76720
getColumnsToShow()to ensure required columns (AVATAR and GROUP_TAG) are always included when grouping by tagApp/src/libs/SearchUIUtils.ts
Lines 3209 to 3224 in 5b76720
GROUP_TAGingetSearchColumnTranslationKey()that returns the tag translation keyApp/src/libs/SearchUIUtils.ts
Lines 2628 to 2708 in 5b76720
GROUP_TAGto the required columns set so it cannot be hidden on theSearch Columns PageApp/src/pages/Search/SearchColumnsPage.tsx
Lines 58 to 64 in 5b76720
TAGingetTransactionGroupHeaders()that returns the appropriate column header configurationApp/src/components/SelectionListWithSections/SearchTableHeader.tsx
Lines 263 to 310 in 5b76720
SearchCustomColumnIdstype to include the tag custom column valuesApp/src/components/Search/types.ts
Lines 117 to 122 in 5b76720
Test Branch
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.
13 remaining items
neil-marcellini commentedon Jan 27, 2026
@ShridharGoel is assigned as C+
melvin-bot commentedon Jan 28, 2026
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.
melvin-bot commentedon Jan 29, 2026
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.
melvin-bot commentedon Jan 29, 2026
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.
trjExpensify commentedon Feb 5, 2026
Settling up with Shridhar at the end, closing!
mkhutornyi commentedon Feb 24, 2026
@trjExpensify can I get payment summary for reviewing linked PR?
trjExpensify commentedon Feb 27, 2026
Payment summary as follows:
Go ahead and request!
quinthar commentedon Mar 28, 2026
Approved $250 to @mkhutornyi