Skip to content

Standardize Expense Report and Expense header with predictable button placement and carousel counter #90366

Open

Description

@shawnborton

We have mixed styles for showing the carousel counter on the expense report header as well as the expense header. Sometimes the carousel counter has a "X of X" label, though it doesn't on expenses. We also don't always show the expense carousel counter when you view expenses from the Spend page - we only show it when you view an expense from within an expense report.

We also show the carousel counter buttons on the same line as the next steps, which feels counter intuitive given that the carousel counter is more of a parent item not attached to next steps.

We'd like to standardize on the buttons here across the two types: expense reports and expenses:

Image

Notable changes:

  • Let's move the report buttons to be down near the report next steps, on the same vertical line
  • Let's always have the carousel buttons in the top right
  • Let's make sure we always show the carousel for expenses when you access expenses from the Spend page, the same way you see a carousel when accessing Reports from the Reports page

Once we have this framework in place, we'll be able to do things like launch a violation fixer from Home that will always have a consistent carousel button placement.

cc @JmillsExpensify @trjExpensify @dannymcclain @dubielzyk-expensify

Issue OwnerCurrent Issue Owner: @thelullabyy

Activity

  1. shawnborton commented on May 12, 2026

    @shawnborton
    ContributorAuthor

    Discussed in Slack, @thelullabyy will implement and @ShridharGoel will review.

  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    NewFeatureSomething to build that is a new item.
    on May 12, 2026
  3. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 12, 2026
  4. KJ21-ENG commented on May 12, 2026

    @KJ21-ENG
  5. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 12, 2026
  6. thelullabyy commented on May 17, 2026

    @thelullabyy
    Contributor

    @ShridharGoel PR is ready for review

  7. 141 remaining items

  8. changed the title [-]Standardize Expense Report and Expense header with predictable button placement and carousel counter[/-] [+][Due for payment 2026-10-13] Standardize Expense Report and Expense header with predictable button placement and carousel counter[/+] on Oct 6, 2026
  9. melvin-bot commented on Oct 6, 2026

    @melvin-bot

    @thelullabyy

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.3-4 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-10-13. 🎊

    Contributor+ Checklist: The following checklist (instructions) needs to be completed before this issue can be closed:

    • [@thelullabyy] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

    If no checklist is needed for this issue, use the K2 [no checklist button].

  10. melvin-bot commented on Oct 9, 2026

    @melvin-bot

    @thelullabyy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  11. JS00001 commented on Oct 12, 2026

    @JS00001
    Contributor

    This is on production. All of these follow ups are still in progress though: #103200

  12. melvin-bot commented on Oct 12, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  13. changed the title [-][Due for payment 2026-10-13] Standardize Expense Report and Expense header with predictable button placement and carousel counter[/-] [+]Standardize Expense Report and Expense header with predictable button placement and carousel counter[/+] on Oct 14, 2026
  14. removed their assignment
    on Oct 14, 2026
  15. mallenexpensify commented on Oct 14, 2026

    @mallenexpensify
    Contributor

    Please comment and tag me if/when payment is due, thx

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

Metadata

Metadata

Labels

DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.Overdue

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions