-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-04-03] [HOLD for payment 2023-03-31] Chat - Members names overlapping the group conversation header. #16376
Comments
Triggered auto assignment to @adelekennedy ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @marcaaron ( |
Issue is not reproduced in Production, adding Deploy Blocker Screen_Recording_20230321_193619_Chrome.mp4 |
This was introduced on this line By the PR here: https://github.com/Expensify/App/pull/15646/files |
Seems like the same issue was reported here earlier. |
Working on a revert of the offending PR |
@tienifr can you comment here so I can assign you? |
Oke. Thanks |
Is this resolved? If so can you remove the label and check this off here please? #16345 |
Yes, this is resolved. Removing the label and checking off |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.88-2 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 2023-03-31. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Regression Test ProposalBug: Chat - Members names overlapping the group conversation header. Proposed Test Steps:
Do we 👍 or 👎 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.89-0 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 2023-04-03. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
@alex-mechler, @marcaaron, @adelekennedy, @tienifr Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I think it's not overdue - just waiting for the regression period to be over. |
I think the regression period is over now. |
This was a regression from #15646, so I don't believe there is any payments due here. This was caught by applause |
@alex-mechler, @marcaaron, @adelekennedy, @tienifr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
1 similar comment
@alex-mechler, @marcaaron, @adelekennedy, @tienifr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Ok, so I think we can close it then. Reopen if anyone disagrees. |
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:
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?
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
The text was updated successfully, but these errors were encountered: