Skip to content

[Due for payment 2026-02-04] [$250] [Insights] [Release 1] Top Categories - Add group-by:category #80034

Closed

Description

@neil-marcellini

Frontend Release 1: Add “Top Categories” suggested search

Follow the same pattern as "Top Spenders"

  1. Add the ability to Group By Category from Reports > Expenses (group-by:category)
    1. Follow the pattern used for group-by:from in Top Spenders.
    2. src/CONST/index.ts - Add CATEGORY: 'category' to CONST.SEARCH.GROUP_BY
    3. src/languages/en.ts (and all language files) - Add [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Category' to search.filters.groupBy
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022013727811217867154
  • Upwork Job ID: 2013727811217867154
  • Last Price Increase: 2026-01-20
Issue OwnerCurrent Issue Owner: @trjExpensify / @stephanieelliott

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    NewFeatureSomething to build that is a new item.
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 20, 2026
  2. melvin-bot commented on Jan 20, 2026

    @melvin-bot
  3. changed the title [-][Insights] [Release 1] Top Categories - Add group-by:category[/-] [+][$250] [Insights] [Release 1] Top Categories - Add group-by:category[/+] on Jan 20, 2026
  4. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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.

  5. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (External)

  6. 39 remaining items

  7. melvin-bot commented on Jan 28, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  8. neil-marcellini commented on Jan 28, 2026

    @neil-marcellini
    ContributorAuthor
  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 28, 2026
  10. changed the title [-][$250] [Insights] [Release 1] Top Categories - Add group-by:category[/-] [+][Due for payment 2026-02-04] [$250] [Insights] [Release 1] Top Categories - Add group-by:category[/+] on Jan 28, 2026
  11. melvin-bot commented on Jan 28, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Jan 28, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.10-6 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 2026-02-04. 🎊

    For reference, here are some details about the assignees on this issue:

    • @Ollyws requires payment through NewDot Manual Requests
    • @ShridharGoel requires payment through NewDot Manual Requests
    • @TaduJR requires payment (Needs manual offer from BZ)
  13. melvin-bot commented on Jan 28, 2026

    @melvin-bot

    BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  14. melvin-bot commented on Jan 29, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  15. melvin-bot commented on Jan 29, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  16. trjExpensify commented on Feb 5, 2026

    @trjExpensify
    Contributor

    Settling up with Tadu and Shridhar at the end, closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions