Skip to content

[Due for payment 2025-08-26] [Suggested Search v2.4] [App] Add Group By Exposed Filter #64465

Closed

Description

@JS00001

Implement this section of the design doc

Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. self-assigned this
    on Jun 18, 2025
  2. melvin-bot commented on Jun 18, 2025

    @melvin-bot

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

  3. moved this to Second Cohort - HIGH in [#whatsnext] #migrateon Jun 24, 2025
  4. JS00001 commented on Jun 27, 2025

    @JS00001
    ContributorAuthor

    This is deployed, but also hidden behind a dev lock while waiting for BE changes

  5. 20 remaining items

  6. changed the title [-][Suggested Search v2.4] [App] Add Group By Exposed Filter[/-] [+][Due for payment 2025-08-26] [Suggested Search v2.4] [App] Add Group By Exposed Filter[/+] on Aug 19, 2025
  7. melvin-bot commented on Aug 19, 2025

    @melvin-bot

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

  8. melvin-bot commented on Aug 19, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.96-2 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 2025-08-26. 🎊

  9. melvin-bot commented on Aug 19, 2025

    @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:

    • [@luacmartins / @JS00001] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
  10. melvin-bot commented on Aug 26, 2025

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  11. luacmartins commented on Aug 28, 2025

    @luacmartins
    Contributor

    We handled payment for this in #64472. Closing.

  12. moved this from Second Cohort - HIGH to Done in [#whatsnext] #migrateon Aug 28, 2025
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 productionDailyKSv2NewFeatureSomething to build that is a new item.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions