Skip to content

[Due for Payment 4th Dec] Android & iOS - Expense - Report subtitle "From #report in workspace" is aligned to the left #72636

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.2.31-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1291/folder/13177029/41237792/952581437
Email or phone of affected tester (no customers): sdijsnoisjnosij@gmail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Money Requests

Action Performed:

  1. Launch Expensify app.
  2. Go to workspace chat.
  3. Create two expenses in the workspace chat.
  4. Open the expense report.
  5. Open any transaction thread.
  6. Tap on the report header.

Expected Result:

Report subtitle "From #report in workspace" will be aligned to the center (web, mweb and desktop).

Actual Result:

Report subtitle "From #report in workspace" is aligned to the left (Android & iOS).

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

Image
Bug6974997_1760476864457.Screen_Recording_20251015_051635_Expensify.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @trjExpensify (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 Oct 14, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 14, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 14, 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. 17 remaining items

  7. lorretheboy commented on Nov 10, 2025

    @lorretheboy
    Contributor

    Please check this PR. Thanks @suneox

  8. melvin-bot commented on Dec 4, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @suneox, @trjExpensify, @lakchote eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Dec 9, 2025
  10. changed the title [-]Android & iOS - Expense - Report subtitle "From #report in workspace" is aligned to the left[/-] [+][Due for Payment 4th Dec] Android & iOS - Expense - Report subtitle "From #report in workspace" is aligned to the left[/+] on Dec 9, 2025
  11. trjExpensify commented on Dec 9, 2025

    @trjExpensify
    Contributor

    Automation failed here. Are we processing anything here or was this a regression of #71549 and handled there?

  12. suneox commented on Dec 11, 2025

    @suneox
    Contributor

    Automation failed here. Are we processing anything here or was this a regression of #71549 and handled there?

    Since this is a regression of #71549, we can proceed with closing this issue

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.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions