Skip to content

[Due for payment 2026-09-16] Clean up Home's For you and Time sensitive sections by combining them #99775

Closed

Description

@shawnborton

We'd like to take a stab at cleaning up the items on Home a bit, particularly in the main card. Now that we have the greeting and Concierge box, it makes less sense to also have a section header for For you and Time sensitive.

Can we try something where we essentially combine the Time sensitive and For you sections into one single section? We'd always keep the Time sensitive rows at the top, and always keep RBR rows above GBR rows. We'd also remove the label above the rows.

(We also want to remove the background from the icon avatars to keep things more consistent with MenuItems elsewhere).

The result is something like this:

Image

cc @dannymcclain @dubielzyk-expensify @JmillsExpensify

Issue OwnerCurrent Issue Owner: @ZhenjaHorbach

Activity

  1. adamgrzybowski commented on Sep 1, 2026

    @adamgrzybowski
    Contributor

    👋 You can assign me

  2. changed the title [-]Clean up Home's For you and Time sensitive sections by combing them[/-] [+]Clean up Home's For you and Time sensitive sections by combining them[/+] on Sep 1, 2026
  3. adamgrzybowski commented on Sep 1, 2026

    @adamgrzybowski
    Contributor

    @shawnborton quick questions

    1. Should there be one shared "see more" limit for the merged list? I am assuming yes, but we can adjust if necessary
    2. What to do with empty states? I am assuming that we should show an empty state only when both "for you" and "time sensitive" are empty?
  4. dannymcclain commented on Sep 1, 2026

    @dannymcclain
    Contributor

    #notShawn I think yes to both of those. We can stick with the empty state(s) we currently use in the "For you" section, but it will apply to that whole block.

  5. shawnborton commented on Sep 1, 2026

    @shawnborton
    ContributorAuthor
  6. adamgrzybowski commented on Sep 2, 2026

    @adamgrzybowski
    Contributor

    What about titles? Some rows have them and some don't. Should I remove them?

    Image

    cc: Not @dannymcclain and not @shawnborton 😄

  7. dannymcclain commented on Sep 2, 2026

    @dannymcclain
    Contributor

    What about titles? Some rows have them and some don't. Should I remove them?

    @shawnborton @JmillsExpensify I think we talked about removing them (in Slack)—does that sound right to y'all?

  8. 23 remaining items

  9. added
    ReviewingHas a PR in review
    and removed on Sep 4, 2026
  10. melvin-bot commented on Sep 7, 2026

    @melvin-bot

    Triggered auto assignment to @iwiznia, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  11. self-assigned this
    on Sep 7, 2026
  12. adamgrzybowski commented on Sep 9, 2026

    @adamgrzybowski
    Contributor

    This one is merged @grgia

  13. moved this from Backlog to Done in Home pageon Sep 9, 2026
  14. added and removed
    ReviewingHas a PR in review
    on Sep 9, 2026
  15. changed the title [-]Clean up Home's For you and Time sensitive sections by combining them[/-] [+][Due for payment 2026-09-16] Clean up Home's For you and Time sensitive sections by combining them[/+] on Sep 9, 2026
  16. melvin-bot commented on Sep 9, 2026

    @melvin-bot

    @ZhenjaHorbach

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.74-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 2026-09-16. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  17. melvin-bot commented on Sep 22, 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.

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

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions