Skip to content

Spend - Report count is not shown on the collapsed sidebar when section is collapsed #92819

Closed

Description

@applause-bot

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.4.0-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91974
Email or phone of affected tester (no customers): osidnjosjoidjiosjdo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Spend > Expenses.
  5. Collapse Expense reports.
    → Report count is shown on the collapsed section.
  6. Collapse the sidebar.

Expected Result:

Report count will be shown on the collapsed sidebar when section is collapsed.

Actual Result:

Report count is not shown on the collapsed sidebar when section is collapsed.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7172881_1780683527488.2.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7172881

Issue OwnerCurrent Issue Owner: @dubielzyk-expensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 5, 2026
  2. applause-bot commented on Jun 5, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/eade174f3f599e02013c436c674ec376da01ef10445e7062ca1918656e5ac4d2

  3. melvin-bot commented on Jun 5, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #91974

  4. melvin-bot commented on Jun 5, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jun 5, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 5, 2026
  7. blimpich commented on Jun 5, 2026

    @blimpich
    Contributor

    This isn't a bug, the OG issue description doesn't show any report count number in the design. @dubielzyk-expensify it is an interesting idea though? Do we want to add this?

  8. MelvinBot commented on Jun 5, 2026

    @MelvinBot
  9. 1 remaining item

  10. KJ21-ENG commented on Jun 5, 2026

    @KJ21-ENG
    Contributor

    This isn't a bug, the OG issue description doesn't show any report count number in the design. @dubielzyk-expensify it is an interesting idea though? Do we want to add this?

    Sounds cool though 💯

  11. melvin-bot commented on Jun 5, 2026

    @melvin-bot

    Current assignee @dubielzyk-expensify is eligible for the Design assigner, not assigning anyone new.

  12. blimpich commented on Jun 5, 2026

    @blimpich
    Contributor

    Assigning Jon as designer to see if we'd want to add this functionality, since it is new and not included in the original design.

    @dubielzyk-expensify do you think we should add this?

  13. godzillaxbox19982014-lgtm commented on Jun 6, 2026

    @godzillaxbox19982014-lgtm
  14. blimpich commented on Jun 8, 2026

    @blimpich
    Contributor

    @godzillaxbox19982014-lgtm I'm marking your comment as spam because if you had read the discussion here you would realize that we are still discussing what the best path forward here is, or if we even want to do it. Please either be more prudent or make your AI more context aware.

  15. godzillaxbox19982014-lgtm commented on Jun 8, 2026

    @godzillaxbox19982014-lgtm
  16. dubielzyk-expensify commented on Jun 8, 2026

    @dubielzyk-expensify
    Contributor

    This is not a bug. I could see us doing the badge but it'd look very funky as it'd be floating in a weird space if we wanna keep the positioning consistent:

    Image

    Curious if @Expensify/design has any ideas, otherwise I think we can leave this closed

  17. shawnborton commented on Jun 8, 2026

    @shawnborton
    Contributor

    Yeah I'm with you, I think we just leave this one closed for now

  18. KJ21-ENG commented on Jun 8, 2026

    @KJ21-ENG
    Contributor

    Agreed as well, Its looking very weird 😅

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2DesignEngineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions