Add support for groupBy week in Search by cristipaval · Pull Request #80684 · Expensify/App

cristipaval · 2026-01-27T22:02:38Z

Explanation of Change

Fixed Issues

$ #80396
PROPOSAL:

Tests

Prerequisites:

Ensure you have expenses with dates spanning multiple weeks (e.g., expenses from different weeks in January, February, March)
Ensure you have expenses from different days of the week, especially Sunday (critical for week grouping)
Ensure you have expenses from different years if testing across year boundaries

Test 1: Access Group by Week via Advanced Filters

Open the app and navigate to the Reports page
Go to Expense Section
Tap the filter in the search header
Tap on "Group by" option
Verify "Week" appears in the list of group by options
Select "Week"
Tap "Save"
Verify expenses are now grouped by week with headers showing:
- Week date range (e.g., "Jan 25 - Jan 31, 2026", "Feb 1 - Feb 7, 2026")
- Number of expenses in that week
- Total amount for that week

Test 2: Verify Week Grouping Display (Large Screen)

Open the app on desktop/web or tablet in landscape mode
Go to Expense Section
Navigate to Search and apply groupBy:week filter
Verify the table header shows: Week icon | Week | Expenses | Total
Verify each week row displays the calendar icon, week date range (e.g., "Jan 25 - Jan 31, 2026"), expense count, and total amount
Verify columns are properly aligned between header and rows

Test 3: Verify Week Grouping Display (Small Screen)

Open the app on mobile device
Go to Expense Section
Navigate to Search and apply groupBy:week filter
Verify each week shows the calendar icon, week date range, and total amount
Tap the expand arrow on a week row
Verify the individual transactions within that week are displayed

Test 4: Verify Week Grouping Across Multiple Weeks

Create expenses with dates spanning at least 3 different weeks
Go to Expense Section
Navigate to Search with groupBy:week
Verify expenses are grouped into separate week sections
Verify each week section shows the correct week date range
Verify transactions appear only in their respective week groups

Test 5: Verify Week Expand/Collapse

Navigate to Search with groupBy:week applied
Tap/click on a week row (e.g., "Jan 25 - Jan 31, 2026")
Verify the week row expands to show individual transactions within that week
Tap/click on the week row again
Verify the week row collapses to hide the transactions

Test 6: Verify Sorting

Navigate to Search with groupBy:week
Verify weeks are sorted chronologically (newest first by default, e.g., "Feb 1 - Feb 7, 2026", "Jan 25 - Jan 31, 2026", "Jan 18 - Jan 24, 2026")
Click on the "Week" column header to sort
Verify weeks sort chronologically (oldest first, then newest first on second click)
Click on the "Total" column header
Verify weeks sort by total amount (descending, then ascending on second click)

Test 7: Verify Multi-select Checkbox

Navigate to Search with groupBy:week
Enable selection mode (long press on mobile, or use bulk select)
Tap the checkbox on a week header row
Verify all transactions within that week become selected

Test 8: Verify Week Grouping Across Year Boundaries

Create expenses with dates spanning December 28, 2025 - January 3, 2026 (a week that crosses year boundary)
Go to Expense Section
Navigate to Search with groupBy:week
Verify expenses are grouped into a single week section showing cross-year date range (e.g., "Dec 28, 2025 - Jan 3, 2026")
Verify transactions appear only in their respective week groups
Verify weeks are sorted correctly across year boundaries (newest first)

Test 9: Verify Sunday Transaction Grouping (Critical Edge Case)

Create an expense on Sunday, January 25, 2026
Create expenses on other days of that week (Monday Jan 26, Wednesday Jan 28, Saturday Jan 31)
Go to Expense Section
Navigate to Search with groupBy:week
Verify all expenses from Sunday Jan 25 through Saturday Jan 31 appear in the same week group
Verify the week group shows date range starting with Sunday (e.g., "Jan 25 - Jan 31, 2026")
Verify the Sunday transaction is NOT grouped into the previous week

Test 10: Verify Clicking Week Group Filters Transactions

Navigate to Search with groupBy:week
Click/tap on a week group header (e.g., "Jan 25 - Jan 31, 2026")
Verify the search query updates to filter by that week's date range
Verify groupBy is removed from the query
Verify only transactions from that week are displayed as individual items (not grouped)
Verify the date filter shows the week's start and end dates

Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as steps.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-01-27.at.17.34.11.mov

…yWeek

OSBotify · 2026-01-27T22:03:42Z

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff

diff --git a/src/languages/de.ts b/src/languages/de.ts
index 6c88f168..6fe752b8 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -638,6 +638,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Doppelte Ausgabe',
         newFeature: 'Neue Funktion',
         month: 'Monat',
+        week: 'Woche',
     },
     supportalNoAccess: {
         title: 'Nicht so schnell',
@@ -6956,6 +6957,7 @@ Fordere Spesendetails wie Belege und Beschreibungen an, lege Limits und Standard
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Auszahlungs-ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategorie',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Monat',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Woche',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 7f08b053..d2f21ef9 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -640,6 +640,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Note de frais en double',
         newFeature: 'Nouvelle fonctionnalité',
         month: 'Mois',
+        week: 'Semaine',
     },
     supportalNoAccess: {
         title: 'Pas si vite',
@@ -6967,6 +6968,7 @@ Exigez des informations de dépense comme les reçus et les descriptions, défin
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de retrait',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Catégorie',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mois',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Semaine',
             },
             feed: 'Flux',
             withdrawalType: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 7525885d..52b6b8ce 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -639,6 +639,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Spesa duplicata',
         newFeature: 'Nuova funzionalità',
         month: 'Mese',
+        week: 'Settimana',
     },
     supportalNoAccess: {
         title: 'Non così in fretta',
@@ -6945,6 +6946,7 @@ Richiedi dettagli di spesa come ricevute e descrizioni, imposta limiti e valori
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID prelievo', //_/\__/_/  \_,_/\__/\__/\_,_/
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mese',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Settimana',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 43f10ab5..789bba5b 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -638,6 +638,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: '重複した経費',
         newFeature: '新機能',
         month: '月',
+        week: '週',
     },
     supportalNoAccess: {
         title: 'ちょっと待ってください',
@@ -6882,9 +6883,10 @@ ${reportName}
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: '差出人',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'カード',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金ID',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金 ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'カテゴリ',
                 [CONST.SEARCH.GROUP_BY.MONTH]: '月',
+                [CONST.SEARCH.GROUP_BY.WEEK]: '週',
             },
             feed: 'フィード',
             withdrawalType: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 5289966a..900a0d20 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -639,6 +639,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Dubbele uitgave',
         newFeature: 'Nieuwe functie',
         month: 'Maand',
+        week: 'Week',
     },
     supportalNoAccess: {
         title: 'Niet zo snel',
@@ -6927,6 +6928,7 @@ Vraag verplichte uitgavedetails zoals bonnetjes en beschrijvingen, stel limieten
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Opname-ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categorie',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Maand',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Week',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index a3772656..307f5200 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -639,6 +639,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Zduplikowany wydatek',
         newFeature: 'Nowa funkcja',
         month: 'Miesiąc',
+        week: 'Tydzień',
     },
     supportalNoAccess: {
         title: 'Nie tak szybko',
@@ -6917,6 +6918,7 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID wypłaty',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategoria',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Miesiąc',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Tydzień',
             },
             feed: 'Kanał',
             withdrawalType: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ee7cd0e6..55737c17 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -638,6 +638,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Despesa duplicada',
         newFeature: 'Novo recurso',
         month: 'Mês',
+        week: 'Semana',
     },
     supportalNoAccess: {
         title: 'Não tão rápido',
@@ -6915,9 +6916,10 @@ Exija detalhes de despesas como recibos e descrições, defina limites e padrõe
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'De',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Cartão',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de retirada',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de saque',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mês',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Semana',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index ee322f52..e70328a2 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -635,6 +635,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: '重复报销',
         newFeature: '新功能',
         month: '月',
+        week: '周',
     },
     supportalNoAccess: {
         title: '先别急',
@@ -6760,11 +6761,13 @@ ${reportName}
             reimbursable: '可报销',
             purchaseCurrency: '购买货币',
             groupBy: {
-                [CONST.SEARCH.GROUP_BY.FROM]: '来自',
+                [CONST.SEARCH.GROUP_BY.FROM]: '发件人',
                 [CONST.SEARCH.GROUP_BY.CARD]: '卡',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '提现 ID',
+                //_/\__/_/  \_,_/\__/\__/\_,_/
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '提现编号',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: '类别',
                 [CONST.SEARCH.GROUP_BY.MONTH]: '月',
+                [CONST.SEARCH.GROUP_BY.WEEK]: '周',
             },
             feed: '动态',
             withdrawalType: {

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

…yWeek

codecov · 2026-01-28T01:00:03Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/CONST/index.ts	`87.39% <ø> (ø)`
...tionListWithSections/Search/BaseListItemHeader.tsx	`100.00% <ø> (ø)`
...stWithSections/Search/TransactionGroupListItem.tsx	`71.69% <ø> (ø)`
...tionListWithSections/Search/WeekListItemHeader.tsx	`100.00% <100.00%> (ø)`
src/libs/DateUtils.ts	`63.21% <100.00%> (+1.08%)`	⬆️
src/styles/utils/index.ts	`49.56% <100.00%> (+0.07%)`	⬆️
...ts/SelectionListWithSections/SearchTableHeader.tsx	`5.79% <0.00%> (-0.18%)`	⬇️
src/components/Search/SearchList/index.tsx	`3.00% <0.00%> (-0.20%)`	⬇️
src/components/Search/index.tsx	`31.74% <0.00%> (-1.32%)`	⬇️
src/libs/SearchParser/searchParser.js	`73.87% <71.97%> (-0.67%)`	⬇️
... and 2 more
... and 10 files with indirect coverage changes

melvin-bot · 2026-01-28T01:37:08Z

@shubham1206agra Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

cristipaval · 2026-01-28T16:06:12Z

ready again for review, @shubham1206agra 🙏

shubham1206agra · 2026-01-28T17:26:43Z

@cristipaval The count and expenses under mismatch when doing year to date filter with week group by.

shubham1206agra · 2026-01-28T17:58:44Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
xIf a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-01-28.at.11.27.38.PM.mov

melvin-bot · 2026-01-28T18:01:56Z

@Valforte Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

…yWeek

OSBotify · 2026-01-28T22:30:19Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-01-28T23:23:28Z

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.11-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

mitarachim · 2026-01-29T04:29:46Z

@cristipaval This PR is failing because of a regression issue #80846 and #80849

The issue is reproducible in: Web, Android , iOS

Evidence for 80846 :

Bug7060819_1769654599148.Sunday_expense_not_shown.mp4

Bug7060819_1769654451891.Sunday_expense_is_misssing.mp4

Evidence for 80849 :

Bug7060828_1769656443529.80684-Search_Query_Is_Not_Updated.mp4

Bug7060828_1769656336595.search_quey_is_not_updated_when_click_on_the_list_header.mp4

OSBotify · 2026-02-05T20:23:08Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.3.12-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

cristipaval added 4 commits January 27, 2026 10:39

Add groupby:week

cb6fb32

Merge branch 'cristi_support-groupByMonth' into cristi_support-groupB…

63bd122

…yWeek

Fix week groupping sorting

9dd115f

Merge remote-tracking branch 'origin/main' into cristi_support-groupB…

ec7a821

…yWeek

cristipaval self-assigned this Jan 27, 2026

cristipaval added 9 commits January 27, 2026 14:46

Fix formatted week display

6ac4d62

Fix expanding the week groups

144834c

Prettier

3a57c88

Fix week start and end dates

2ebab4c

Add translations

af9eb56

Merge remote-tracking branch 'origin/main' into cristi_support-groupB…

5f2037f

…yWeek

UI test

baa97ba

Tests

e1144cd

Run prettier

2a47570

cristipaval added 4 commits January 27, 2026 17:03

Fix typecheck

e4f0393

Fix ESLisnt

6c2b059

prettier

707ac24

FIx sorting

68ad91a

cristipaval marked this pull request as ready for review January 28, 2026 01:37

cristipaval requested review from a team as code owners January 28, 2026 01:37

melvin-bot bot requested review from JmillsExpensify and shubham1206agra and removed request for a team and JmillsExpensify January 28, 2026 01:37

melvin-bot bot removed the request for review from a team January 28, 2026 01:37

shubham1206agra approved these changes Jan 28, 2026

View reviewed changes

melvin-bot bot requested a review from Valforte January 28, 2026 18:01

cristipaval added 2 commits January 28, 2026 12:08

fix test

bdf0776

Fix the week intervals when the date is limited

2dd02bf

cristipaval requested review from puneetlath and removed request for Valforte January 28, 2026 20:17

cristipaval added 2 commits January 28, 2026 12:18

Merge remote-tracking branch 'origin/main' into cristi_support-groupB…

60ce8cc

…yWeek

Regenerate after resolving conflicts

b35710c

puneetlath previously approved these changes Jan 28, 2026

View reviewed changes

Fix eslint

3263002

cristipaval dismissed puneetlath’s stale review via 3263002 January 28, 2026 21:15

Merge remote-tracking branch 'origin/main' into cristi_support-groupB…

2f6f778

…yWeek

cristipaval requested a review from puneetlath January 28, 2026 22:18

puneetlath approved these changes Jan 28, 2026

View reviewed changes

puneetlath merged commit 8cc7133 into main Jan 28, 2026
35 checks passed

puneetlath deleted the cristi_support-groupByWeek branch January 28, 2026 22:20

OSBotify mentioned this pull request Jan 28, 2026

Deploy Checklist: New Expensify 2026-01-28 #80808

Closed

OSBotify mentioned this pull request Jan 28, 2026

[Insights] Reports - Expense report does not open #80814

Closed

7 tasks

mitarachim mentioned this pull request Jan 28, 2026

Reports - Missing Group columns in Week filter #80818

Closed

7 tasks

puneetlath mentioned this pull request Jan 28, 2026

[CP Staging] Revert "Add support for groupBy week in Search" #80824

Merged

mitarachim mentioned this pull request Jan 29, 2026

[Insights] Reports-Expense on Sunday is not displayed in groupby list #80846

Closed

7 tasks

mitarachim mentioned this pull request Jan 29, 2026

Reports-Search query does not update when click on week group header #80849

Closed

7 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add support for groupBy week in Search#80684

Add support for groupBy week in Search#80684
puneetlath merged 32 commits intomainfrom
cristi_support-groupByWeek

cristipaval commented Jan 27, 2026 •

edited

Loading

Uh oh!

OSBotify commented Jan 27, 2026

Uh oh!

codecov bot commented Jan 28, 2026 •

edited by github-actions bot

Loading

Uh oh!

melvin-bot bot commented Jan 28, 2026

Uh oh!

cristipaval commented Jan 28, 2026

Uh oh!

shubham1206agra commented Jan 28, 2026

Uh oh!

shubham1206agra commented Jan 28, 2026

Uh oh!

melvin-bot bot commented Jan 28, 2026

Uh oh!

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

mitarachim commented Jan 29, 2026 •

edited

Loading

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

cristipaval commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

OSBotify commented Jan 27, 2026

🦜 Polyglot Parrot! 🦜

Uh oh!

codecov bot commented Jan 28, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot bot commented Jan 28, 2026

Uh oh!

cristipaval commented Jan 28, 2026

Uh oh!

shubham1206agra commented Jan 28, 2026

Uh oh!

shubham1206agra commented Jan 28, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 28, 2026

Uh oh!

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

mitarachim commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

cristipaval commented Jan 27, 2026 •

edited

Loading

codecov bot commented Jan 28, 2026 •

edited by github-actions bot

Loading

mitarachim commented Jan 29, 2026 •

edited

Loading