Skip to content

[$50] Reports - User name in To and From field overlaps with other field after Category row is added #61145

Closed

Description

@mitarachim

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.1.38-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): jsdoijnsoisndo1@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Log in with a new Gmail account.
  3. Select Skip on work email step.
  4. Select Something else and complete the onboarding.
  5. Open 1:1 DM.
  6. Submit an expense to the user.
  7. Go to Reports.
  8. Go offline.
  9. Go to Account > Workspaces.
  10. Create a new workspace.
  11. Go to Reports.
  12. Go online.

Expected Result:

The user name in From and To field will align correctly when Category row is added to the list header.

Actual Result:

The user name in From and To field is not align correctly when Category row is added to the list header.
The user name in To field overlaps with Category field.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6817298_1745988372691.20250430_123324.mp4
Image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021917507749466250471
  • Upwork Job ID: 1917507749466250471
  • Last Price Increase: 2025-04-30
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 30, 2025
  2. melvin-bot commented on Apr 30, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on Apr 30, 2025

    @melvin-bot

    Triggered auto assignment to @MariaHCD (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Apr 30, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 30, 2025

    @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
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 30, 2025
  7. changed the title [-]Reports - User name in To and From field overlaps with other field after Category row is added[/-] [+][$250] Reports - User name in To and From field overlaps with other field after Category row is added[/+] on Apr 30, 2025
  8. 29 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Apr 30, 2025
  10. mountiny commented on Apr 30, 2025

    @mountiny
    Contributor

    $50 to @daledah

  11. mallenexpensify commented on May 1, 2025

    @mallenexpensify
    Contributor

    @daledah can you please accept the job and reply here once you have?
    https://www.upwork.com/jobs/~021917507749466250471

    (Upwork was acting up, you might have to apply vs accept)

  12. daledah commented on May 2, 2025

    @daledah
    Contributor

    can you please accept the job and reply here once you have?

    @mallenexpensify This was accepted, thanks 🙏

  13. mallenexpensify commented on May 5, 2025

    @mallenexpensify
    Contributor

    @daledah something didn't work, can you please accept the job and reply here once you have?
    https://www.upwork.com/jobs/~021917507749466250471

    I think it should work this time

  14. daledah commented on May 10, 2025

    @daledah
    Contributor

    can you please accept the job

    @mallenexpensify Done!

  15. melvin-bot commented on May 12, 2025

    @melvin-bot

    @mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

  16. mallenexpensify commented on May 13, 2025

    @mallenexpensify
    Contributor

    Contributor: @daledah paid $50 via Upwork

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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions