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.3.84-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91710
Email or phone of affected tester (no customers): applausetester+05272026_1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11/ Chrome
App Component: Other
Action Performed:
- Open the staging.new.expensify.com website.
- Create new report
- Add two expenses to the report and force the second one of them to have a violation
- Go to Spend -> Reports
- Open the created report
- Change sort to Total
Expected Result:
Verify you have the default sort (Date/ASC) set. RBR pre-sort is gone.
Actual Result:
Default sort for Date is set to DESC. RBR pre-sort is still at the top
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
bandicam.2026-05-28.09-08-42-638.1.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7164951
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
Activity
applause-bot commentedon May 28, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/297f145c1eeb20e9d3e55802cae6333624c7b62935f10115ecdb0c62624c9de0
MelvinBot commentedon May 28, 2026
Proposal
What is the root cause of that problem?
The sort toggle logic in
SortableHeaderText.tsx:60always defaults toDESCwhen clicking a column that isn't currently active:When
isActiveisfalse(i.e., switching to a different column), the ternary short-circuits toDESCregardless. So the flow is:MoneyRequestReportTransactionList.tsx:285-288)isActive=false→ sort becomes Total/DESCisActive=false→ sort becomes Date/DESC (bug: should be ASC)What changes do you think we should make in order to solve the problem?
Modify the
nextSortOrderlogic inSortableHeaderText.tsx:60so that when switching to a non-active column, the default sort order isASCinstead ofDESC. The toggle behavior (clicking an already-active column flips the order) should remain unchanged.What alternative solutions did you explore? (Optional)
An alternative would be to handle this in the
onSortPresscallback ofMoneyRequestReportTransactionList.tsx:741by overriding the sort order when the column changes. However, fixing it inSortableHeaderTextis cleaner since it's the shared component responsible for computing the next sort order and the same issue would affect any consumer. Note that this change would also affect the Search table headers that use the same component — this is likely the correct behavior there too (defaulting to ASC when first clicking a column), but should be verified during QA.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.yusufdeveloper2903 commentedon May 28, 2026
🚨 Edited by proposal-police: This proposal was edited at 2026-08-26 09:34:11 UTC.
Proposal
What is the root cause of that problem?
The report transaction table declares its own default sort as Date/ASC, and gates the RBR pre-sort on exactly that pair:
App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
Lines 432 to 438 in 9e84742
The RBR set is
nullfor any other pair, which is what switches violation-first ordering off:App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
Lines 463 to 466 in 9e84742
But the direction a header click produces is not decided here. It is decided by the shared
SortableHeaderText, which anchors the first click of any inactive column toDESC:App/src/components/Search/SortableHeaderText.tsx
Lines 79 to 84 in 9e84742
SortableTableHeaderforwards that order verbatim, and this table'sonSortPresswrites it into state without translating it to the view's own default:App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
Lines 931 to 936 in 9e84742
So after Date → Amount → Date the table lands on
Date/DESC,isDefaultSortstays false, and the flagged expense stops floating to the top.I measured the emitted order rather than inferring it. Rendering the real
MoneyRequestReportTableHeaderin Jest with Amount active and pressing Date emits['date', 'desc'], and driving PR #91710's steps 5 → 7 → 8 through the sameonSortPressbody fails on current main with:When it became wrong
The
DESCanchor is correct for the component's other consumer: Search's own Date sort isDESC.App/src/libs/SearchUIUtils.ts
Line 3306 in 9e84742
The two defaults diverged on 2025-03-24, when this table's initial order was changed from
DESCtoASCin #58903:App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
Lines 78 to 82 in 228e7ab
That made the shared anchor wrong for this view immediately, but with no visible effect until the
isDefaultSortgate gave the lost default a consequence.Why the listed steps do not reproduce it
@rojiphil the OP's step list stops at "Change sort to Total". PR #91710's test plan has an eighth step — "Switch back to Date/ASC and verify RBR-flagged item is back on the top" — and the Applause export dropped it. Following the six listed steps, nothing is wrong.
The second reason it is easy to miss: the Date sort value is
created, which is written date-only.App/src/libs/actions/IOU/MoneyRequest.ts
Line 345 in 9e84742
App/src/libs/ReportUtils.ts
Lines 14103 to 14105 in 9e84742
Two expenses created on the same day compare equal, and
Array.prototype.sortis stable, so ASC and DESC render the same rows in the same order — only the arrow flips. Expenses on different days separate cleanly.On the second sentence of the Actual Result ("RBR pre-sort is still at the top"): with Amount active,
isDefaultSortis false andrbrTransactionIDsisnull— my run asserts that — so nothing pins the flagged row there. If it is still on top, it also wins the amount comparison. That is not a second defect, and a tie-break in the comparator cannot change the sort direction the title is about.Nothing catches it:
SortableHeaderTextandSortableTableHeaderhave no test anywhere intests/, and the only unit test for this component replicates one effect in isolation instead of rendering the header.App/tests/unit/MoneyRequestReportTransactionListActiveTransactionIDsTest.tsx
Lines 36 to 40 in 9e84742
What changes do you think we should make in order to solve the problem?
First, a correction to my own earlier proposal. I suggested a
defaultSortOrderprop onSortableHeaderText. That is wrong: the prop is per table, not per column, so passingASCwould also flip the first click of Amount, Merchant, Description, Category and Tag in this same table. That is a behaviour change well beyond this bug.The default belongs to the view, so the translation belongs in the view. Hoist the pair this file already spells out twice into one constant, and reuse it in the handler:
Only the third hunk changes behaviour. I hoist rather than add a fourth
DATE/ASCliteral because the drift between the two places that spell the default out and the one that did not is the bug.Regression safety:
App/src/components/Search/index.tsx
Lines 975 to 986 in 9e84742
setSortConfighas exactly one call site, the handler above.selectedSortBy !== sortByis false, so repeat clicks still flip ASC↔DESC. Switching to any non-default column still lands on DESC.sortConfigis localuseState, with no API call and nofailureData.sortedTransactions, so it inherits the corrected order with no extra change.One limitation I want to be straight about: a user who deliberately sets Date/DESC, switches to Amount and comes back to Date gets ASC, not the DESC they last chose. The view has one default and this makes it reachable in one click; a second click still gives DESC.
Tests, all of which I ran:
date/ascandisDefaultSorttrue. Fails on current main with the output above, passes with the fix.MoneyRequestReportTransactionListActiveTransactionIDsTest,MoneyRequestReportViewTest,MoneyRequestReportGroupHeaderTest— 15 tests, green with the fix applied.I did not render the whole transaction list in Jest. Test 1 drives the real
MoneyRequestReportTableHeader→SortableTableHeader→SortableHeaderTextchain and reproduces theonSortPressbody verbatim.What alternative solutions did you explore? (Optional)
ASC. Rejected: Search's Date default isDESC, so this makes the shared header wrong for its other consumer, and Search's order is encoded in the URL.defaultSortOrderprop, my earlier proposal. Rejected above: per table rather than per column, so it changes five other columns in this table.MobileMage commentedon May 28, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
In the money request report view (Spend → Reports → open a report), the initial default sort is Date/ASC so that RBR-flagged transactions are surfaced at the top. After clicking the Total column header to change sort, then clicking the Date column header again, Date sorts in DESC order instead of returning to the expected Date/ASC default. This contradicts step 8 of the test plan from the linked PR #91710 ("Switch back to Date/ASC and verify RBR-flagged item is back on the top") because clicking Date no longer restores the table's documented default ordering.
What is the root cause of that problem?
The READ side —
MoneyRequestReportTransactionList— initialisessortConfigwith{sortBy: DATE, sortOrder: ASC}and treats that combination as the "default sort" guard that triggers the RBR pre-sort path. The WRITE side — clicks coming up fromSortableHeaderText— computes the next order with logic that does not know about this table's ASC default:App/src/components/Search/SortableHeaderText.tsx
Lines 60 to 65 in 139b2c8
Line 60 reads
const nextSortOrder = isActive && sortOrder === DESC ? ASC : DESC. When the user clicks a column that is not currently active (isActiveis false becausesortBy === 'total'after step 6, and Date is being re-clicked in step 7), the expression short-circuits to the falsy branch and returnsDESC. The press handler inMoneyRequestReportTransactionListthen writes that order straight into state without translating it to the table's per-column default:App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
Lines 741 to 746 in 139b2c8
The full chain is therefore: user clicks Total →
SortableHeaderTextemits('total', DESC)→ state becomes{sortBy: 'total', sortOrder: 'DESC'}(correct behaviour for non-default columns) → user clicks Date →SortableHeaderTextseesisActive=falsefor Date and emits('date', DESC)→ state becomes{sortBy: 'date', sortOrder: 'DESC'}. BecauseisDefaultSorton line 291 only fires whensortOrder === ASC, the RBR pre-sort path inrbrTransactionIDs(lines 297-311) is also bypassed, so the RBR-flagged transaction no longer floats to the top either. The behaviour inSortableHeaderTextis the right global default for the main Search screen, which usesDESCas itsdefaultSortOrderinSearchUIUtils(line 646), but it is wrong for this specific table whose default is Date/ASC. The mismatch was latent before PR #91710 — the new test plan added the Total → Date round-trip step, which is why staging surfaces it but production (which still ran the old test plan) does not.What changes do you think we should make in order to solve the problem?
Fix it locally inside
MoneyRequestReportTransactionList'sonSortPresshandler so the globalSortableHeaderTextkeeps its existing behaviour for Search (which legitimately defaults to DESC). When the user clicks a column that is not the currently active sort column (i.e.selectedSortBy !== sortBy), use the table's per-column default: ASC whenselectedSortBy === CONST.SEARCH.TABLE_COLUMNS.DATE, otherwise the incomingselectedSortOrder(DESC). When the user clicks the already-active column, honourselectedSortOrderso toggling Date between ASC and DESC still works.App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
Lines 741 to 746 in 139b2c8
Concretely, inside the existing
onSortPresscallback after theisSortableColumnNameguard, computeconst nextOrder = selectedSortBy !== sortBy && selectedSortBy === CONST.SEARCH.TABLE_COLUMNS.DATE ? CONST.SEARCH.SORT_ORDER.ASC : selectedSortOrderand pass that assortOrderintosetSortConfig. This restores the original Date/ASC default on switch-back, which in turn re-armsisDefaultSorton line 291 and re-enables the RBR pre-sort that PR #91710 wanted to validate. The change is scoped to a single handler and a single column, does not modify any shared helper or other Search consumers, and preserves the column-toggle behaviour for repeated clicks on Date (DESC ↔ ASC) because theselectedSortBy !== sortBycheck is false on a re-click of the active column.What alternative solutions did you explore? (Optional)
Adding a per-column default-order map to
SortableHeaderText(so the global component computes ASC for Date and DESC for everything else) was considered but rejected — it would change behaviour for the main Search screen and every other consumer ofSortableTableHeader, where DESC is the intentional default (defaultSortOrder = DESCinSearchUIUtils.ts). Keeping the fix local to the one table that has an ASC default avoids any cross-screen regressions.melvin-bot commentedon May 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil (
External)[-]Spend - Default sort is descending[/-][+][$250] Spend - Default sort is descending[/+]melvin-bot commentedon May 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022059919919895211074
github-actions commentedon May 28, 2026
github-actions commentedon May 28, 2026
192 remaining items
jeffrey-graham commentedon Nov 6, 2026
melvin-bot commentedon Nov 6, 2026
melvin-bot commentedon Nov 6, 2026
@rojiphil Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
bonnhatnguyen commentedon Nov 7, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
In Spend > Reports, when opening an expense report:
ASC) (useMoneyRequestReportSortedTransactions.ts:103-106). However, if the user clicks another column header (such as Total) and then clicks Date again, the Date column sorts in descending (DESC) order instead of returning to its default ascending (ASC) order.useMoneyRequestReportGroupedTransactions.ts), clicking a column header updates the sort direction arrow, butgroupTransactionsByCategory/groupTransactionsByTag(src/libs/ReportLayoutUtils.ts:62-116) always re-sorts the groups alphabetically (A → Z), so when each group contains a single expense (as in the QA reproduction), the visible row order never changes.What is the root cause of that problem?
SortableHeaderTexthardcodesDESCfor any inactive column (src/components/Search/SortableHeaderText.tsx:84&src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:110-115):In
src/components/Search/SortableHeaderText.tsx:84:Whenever a column is not currently active (
isActive === false), clicking it always passesCONST.SEARCH.SORT_ORDER.DESCtoonPress.In
src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:103-115:Because
onSortPressstoresselectedSortOrderdirectly without checking whether the user is switching toCONST.SEARCH.TABLE_COLUMNS.DATEfrom another column, clickingTotal(sortBy: TOTAL, sortOrder: DESC) and then clickingDatesets{sortBy: DATE, sortOrder: DESC}instead of restoring the report table's defaultASCorder forDate.groupTransactionsByCategoryandgroupTransactionsByTagunconditionally overwrite transaction sort order with alphabetical group sorting (src/libs/ReportLayoutUtils.ts:81, 113):In
useMoneyRequestReportGroupedTransactions.ts:256-260,resolvedTransactions(already sorted byuseMoneyRequestReportSortedTransactions) are passed intogroupTransactionsByCategory/groupTransactionsByTag. BecauseMappreserves insertion order,groupsinitially follows the sorted transaction order, butReportLayoutUtils.tsunconditionally callsreturn sortGroupedTransactions(result, localeCompare);at the end of both functions, forcing alphabetical category/tag order regardless of the active column sort.What changes do you think we should make in order to solve the problem?
Restore
CONST.SEARCH.SORT_ORDER.ASCwhen switching to theDATEcolumn insrc/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:110-115:When
selectedSortBy === CONST.SEARCH.TABLE_COLUMNS.DATEandprevState.sortBy !== CONST.SEARCH.TABLE_COLUMNS.DATE, defaultsortOrdertoCONST.SEARCH.SORT_ORDER.ASC(while preserving normalASC <-> DESCtoggling whenDATEis already the active column):(Note: if only the flat-table
Datedefault sort is desired per#101424, this 1-file change inuseMoneyRequestReportSortedTransactions.tscompletely fixes it without touching sharedSortableHeaderText.tsx.)If grouped views should also respect non-default user column sorts (
src/libs/ReportLayoutUtils.ts&useMoneyRequestReportGroupedTransactions.ts):Add an optional
shouldSortGroupsAlphabetically = trueparameter togroupTransactionsByCategoryandgroupTransactionsByTaginsrc/libs/ReportLayoutUtils.ts, and passisDefaultSort(sortBy === CONST.SEARCH.TABLE_COLUMNS.DATE && sortOrder === CONST.SEARCH.SORT_ORDER.ASC) fromuseMoneyRequestReportGroupedTransactions.tsso groups are alphabetized by default but follow the sorted transaction insertion order when the user actively sorts by a column.What alternative solutions did you explore? (Optional)
SortableHeaderText.tsxglobally to default inactive columns toASC:SortableHeaderTextis shared with the main Search page (SearchTableHeader), where clicking an inactive column is expected to start onDESC. Keeping theDATE -> ASCdefault insideuseMoneyRequestReportSortedTransactions.tsavoids regressions in Search.melvin-bot commentedon Nov 7, 2026
📣 @ronanchnlps-bit! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
Burapa-J commentedon Nov 8, 2026
Withdrawn — I'm withdrawing this proposal so I only hold one job at a time, per the contributor guidelines. Thank you for reviewing.
Original proposal
Proposal
Please re-state the problem that we are trying to solve in this issue.
In Spend > Reports, when opening an expense report that has multiple expenses:
ASC) order (Date / ASC).DESC) order instead of restoring its default ascending (ASC) order.sortConfiginsideuseMoneyRequestReportSortedTransactionsis never reset whenreport?.reportIDchanges, switching from a report that was sorted inDESCorder to another report whileMoneyRequestReportTransactionListstays mounted causes the newly opened report to start with descending (DESC) sort instead ofDate / ASC.What is the root cause of that problem?
Inactive Column Clicks Always Emit
DESCinSortableHeaderText.tsxand Are Stored Unchanged inuseMoneyRequestReportSortedTransactions.ts(src/components/Search/SortableHeaderText.tsx:84&src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:103-115):useMoneyRequestReportSortedTransactions.ts:103-106initializes the report table's sort configuration to:SortableHeaderText.tsx:84computes the next sort order for any column press as:!isActive),SortableHeaderTextemitsCONST.SEARCH.SORT_ORDER.DESC.sortBybecomesTOTAL) and then clicks Date (isActiveisfalseforDate),SortableHeaderTextcallsonSortPress(CONST.SEARCH.TABLE_COLUMNS.DATE, CONST.SEARCH.SORT_ORDER.DESC).onSortPress(useMoneyRequestReportSortedTransactions.ts:110-115) blindly storesselectedSortOrder(DESC), overriding the report table's chronologicalDate / ASCdefault.sortConfigPersists Across Report Navigation (src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:103-106):useState<SortConfig>({sortBy: DATE, sortOrder: ASC})only initializes whenMoneyRequestReportTransactionListfirst mounts. If a user sorts a report intoDESCorder and navigates to another report where the component instance is reused acrossreport?.reportIDupdates,sortConfigretains the previous report'sDESCsort state instead of resetting to{sortBy: CONST.SEARCH.TABLE_COLUMNS.DATE, sortOrder: CONST.SEARCH.SORT_ORDER.ASC}.(Note: PR
#101497intentionally removed Red Brick Road violation pre-sorting fromuseMoneyRequestReportSortedTransactions.tsand confirmed that grouped Category/Tag headers inReportLayoutUtils.tsremain alphabetically sorted by design, so neither RBR pre-sorting norsortGroupedTransactionsshould be altered.)What changes do you think we should make in order to solve the problem?
In
src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:Restore
CONST.SEARCH.SORT_ORDER.ASCWhen Switching Back toCONST.SEARCH.TABLE_COLUMNS.DATEinonSortPress(lines 110-115):When switching from another column (
prevState.sortBy !== selectedSortBy) toCONST.SEARCH.TABLE_COLUMNS.DATE, setsortOrdertoCONST.SEARCH.SORT_ORDER.ASC. When clickingDATEwhile it is already the active column (prevState.sortBy === selectedSortBy), useselectedSortOrderso it continues toggling cleanly betweenASCandDESC:Reset
sortConfigtoDate / ASCWhenreport?.reportIDChanges (lines 103-109):Track
report?.reportID(or key the sort state byreport?.reportID) so opening a different report in Spend > Reports always starts on the default{sortBy: CONST.SEARCH.TABLE_COLUMNS.DATE, sortOrder: CONST.SEARCH.SORT_ORDER.ASC}sort.What alternative solutions did you explore? (Optional)
SortableHeaderText.tsx:84globally to default inactive columns toASC: Top-level Search views (Spend > Expenses and Spend > Reports list) intentionally default newly clicked columns toDESC(newest / highest first). ChangingSortableHeaderText.tsxglobally would regress Search sorting and URL query parameters.sortGroupedTransactionsinsrc/libs/ReportLayoutUtils.tsor re-adding RBR violation pre-sorting (proposed by several earlier proposals): PR#101497(fixing#101424) explicitly removed RBR pre-sorting fromuseMoneyRequestReportSortedTransactions.tsand established that category/tag group headers stay in alphabetical order. ModifyingReportLayoutUtils.tsor re-introducing RBR pre-sort would directly regress#101424.cocvn157 commentedon Nov 8, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
In the Money Request Report view (Reports > Spend / Expense Report table view), after sorting expenses by another column (e.g.
TotalorCategory) and then clicking theDatecolumn header, the table sortsDatein descending (DESC) order instead of restoring its default ascending (ASC) order. Additionally, when expenses are grouped by Category or Tag, clicking column headers to sort does not reorder single-transaction groups because groups are always re-sorted alphabetically (A -> Z).What is the root cause of that problem?
There are three connected issues in
MoneyRequestReportView:Datedefaults toDESC(SortableHeaderText.tsx&useMoneyRequestReportSortedTransactions.ts):useMoneyRequestReportSortedTransactions(src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:103-106) initializessortConfigto{sortBy: CONST.SEARCH.TABLE_COLUMNS.DATE, sortOrder: CONST.SEARCH.SORT_ORDER.ASC}. However,SortableHeaderText(src/components/Search/SortableHeaderText.tsx:84) always computesnextSortOrderfor an inactive column (!isActive) asCONST.SEARCH.SORT_ORDER.DESC:When the user sorts by another column and then clicks
Date,onSortPress(useMoneyRequestReportSortedTransactions.ts:110-115) blindly acceptsselectedSortOrder(DESC) instead of startingDateinASCorder to match the table's initial sort order.2. Sort state is not reset when switching reports (
useMoneyRequestReportSortedTransactions.ts:103-106):When
report?.reportIDchanges whileMoneyRequestReportTransactionListremains mounted,sortConfigretains the previous report'ssortBy/sortOrder.3. Grouped mode unconditionally re-sorts groups alphabetically (
ReportLayoutUtils.ts:81, 111):In
groupTransactionsByCategoryandgroupTransactionsByTag(src/libs/ReportLayoutUtils.ts:57-112),Mapinsertion order already reflects the sorted transactions passed in fromuseMoneyRequestReportSortedTransactions, but both functions unconditionally returnsortGroupedTransactions(result, localeCompare), which overrides the user's manual column sort with alphabeticalA -> Zgroup ordering.What changes do you think we should make in order to solve the problem?
src/components/MoneyRequestReportView/useMoneyRequestReportSortedTransactions.ts:hasUserSortedand resetsortConfigto{sortBy: CONST.SEARCH.TABLE_COLUMNS.DATE, sortOrder: CONST.SEARCH.SORT_ORDER.ASC}(andhasUserSortedtofalse) in auseEffectwhenreport?.reportIDchanges.onSortPress, when switching from another column toCONST.SEARCH.TABLE_COLUMNS.DATE(prevState.sortBy !== selectedSortBy && selectedSortBy === CONST.SEARCH.TABLE_COLUMNS.DATE), setsortOrdertoCONST.SEARCH.SORT_ORDER.ASC(while clickingDatewhen it is already active continues to toggleASC <-> DESC):sortOrder: prevState.sortBy !== selectedSortBy && selectedSortBy === CONST.SEARCH.TABLE_COLUMNS.DATE ? CONST.SEARCH.SORT_ORDER.ASC : selectedSortOrder, })); };src/libs/ReportLayoutUtils.ts(groupTransactionsByCategoryandgroupTransactionsByTag) andsrc/components/MoneyRequestReportView/useMoneyRequestReportGroupedTransactions.ts:shouldSortGroupsAlphabetically = trueparameter togroupTransactionsByCategoryandgroupTransactionsByTag, and pass!hasUserSortedfromuseMoneyRequestReportGroupedTransactions:This keeps initial grouped loads sorted alphabetically (
A -> Z) while preserving the sorted transaction order across groups once the user explicitly clicks a column header to sort.What alternative solutions did you explore? (Optional)
SortableHeaderText.tsxglobally so inactive columns default toASC: rejected because the main Search page (SearchPage/SearchColumnConfig) intentionally defaults newly selected columns toDESC. Handling theDATEcolumn transition insideuseMoneyRequestReportSortedTransactionsscopes the behavior to the Money Request Report table without affecting Search.melvin-bot commentedon Nov 8, 2026
📣 @cocvn157! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
melvin-bot commentedon Nov 10, 2026
@rojiphil 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
bingg8684 commentedon Nov 12, 2026
melvin-bot commentedon Nov 12, 2026
📣 @bingg8684! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
github-actions commentedon Nov 12, 2026
melvin-bot commentedon Nov 12, 2026
@rojiphil 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
KFC-19 commentedon Nov 13, 2026
github-actions commentedon Nov 13, 2026