Skip to content

[HOLD for payment 2023-04-03] [HOLD for payment 2023-03-31] Chat - Members names overlapping the group conversation header. #16376

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Login in staging.new.expensify.com and log in with expensifail account
  2. Tap on Fub menu
  3. Select New Group
  4. Select 8 expensifail participants without name
  5. Create a Group

Expected Result:

All text should be correct displayed in page.

Actual Result:

The email address of the participants are overlapping the top header of the group conversation

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.2.88.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:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 21, 2023
  2. MelvinBot commented on Mar 21, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. MelvinBot commented on Mar 21, 2023

    @MelvinBot
    Contributor

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. added
    DeployBlockerCashThis issue or pull request should block deployment
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 21, 2023
  5. OSBotify commented on Mar 21, 2023

    @OSBotify
    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. MelvinBot commented on Mar 21, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  7. kbecciv commented on Mar 21, 2023

    @kbecciv
    Author

    Issue is not reproduced in Production, adding Deploy Blocker

    Screen_Recording_20230321_193619_Chrome.mp4
  8. 23 remaining items

  9. MelvinBot commented on Apr 3, 2023

    @MelvinBot
    Contributor

    @alex-mechler, @marcaaron, @adelekennedy, @tienifr Whoops! This issue is 2 days overdue. Let's get this updated quick!

  10. marcaaron commented on Apr 3, 2023

    @marcaaron
    Contributor

    I think it's not overdue - just waiting for the regression period to be over.

  11. marcaaron commented on Apr 6, 2023

    @marcaaron
    Contributor

    I think the regression period is over now.

  12. alex-mechler commented on Apr 6, 2023

    @alex-mechler
    Contributor

    This was a regression from #15646, so I don't believe there is any payments due here. This was caught by applause

  13. MelvinBot commented on Apr 10, 2023

    @MelvinBot
    Contributor

    @alex-mechler, @marcaaron, @adelekennedy, @tienifr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  14. MelvinBot commented on Apr 10, 2023

    @MelvinBot
    Contributor

    @alex-mechler, @marcaaron, @adelekennedy, @tienifr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  15. marcaaron commented on Apr 10, 2023

    @marcaaron
    Contributor

    Ok, so I think we can close it then. Reopen if anyone disagrees.

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions