-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$1000] [HOLD for payment 2023-05-25] Update LHN/Header for threads to be consistent with design doc #18863
Comments
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.15-12 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-05-25. 🎊 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:
|
Job added to Upwork: https://www.upwork.com/jobs/~01d6dfbcc4cfe1d0e3 |
Triggered auto assignment to @bfitzexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @parasharrajat ( |
Current assignee @stitesExpensify is eligible for the External assigner, not assigning anyone new. |
Sorry for the pings everyone, I should have made this internal from the beginning. @bfitzexpensify can we please pay the C+ $1000 (@rushatgabhane ) |
Thanks! |
Paid out and ended contract. Think we're all done here now, going to close this out. |
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:
Create a thread
Expected Result:
header/lhn should look like this
Actual Result:
Header / lhn looks like this
Workaround:
Usable, but bad UI
Platforms:
Which of our officially supported platforms is this issue occurring on?
all
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: