-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[PAID] mWeb - Top bar color is different #28263
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Everybody was OOO, so I assigned 10 random eligible people. |
ProposalProblemmWeb - Top bar color is different Root CauseI dont think this is a regression, the color is intentionally changed to sidebar(previous color) color which is ChangesWe can replace the color here to the overlay color (or a color decided by design team) instead of sidebar so that the issue can be prevented in future incase the color of overlay changes. |
This should have been covered in #27920. |
No, there was no discussion. |
Normally for these types of regressions we let the contributor who introduced the regression fix it. I commented on the PR raising the issue. No need to block deploy on this, since it's such a minor display bug. |
@ishpaul777 We need to fix this app wide and not limited to the sidebar. e.g. if you got to a chat and press the plus grey button a modal will appear and the status bar color won't much. Can you please update your proposal addressing this? |
@s77rt The changes suggested will also changes the statusbar color app wide to overlay color. (#1A3D32) ![]() |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.76-6 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-10-10. 🎊 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.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Triggered auto assignment to @strepanier03 ( |
Bug0 Triage Checklist (Main S/O)
|
Assigning |
Thanks, @jasperhuangg - I'll work on this now since it's two days past the payment date. I'll have an update soon. |
@jasperhuangg - Quick question here. I see that the PR was submitted by @ishpaul777 but they aren't listed as the contributor here, not are they assigned to this GH. I don't want to shortchange them and not pay when we should. Do you have any context into why they aren't listed as needing payment? Was there some special circumstances here that I'm missing? |
This was regression from my PR, unless I am missing something(this was first time i fixed a regression) no payment requires for regression fixes. |
@strepanier03 No payment is due here except for the bug reporter |
@Beamanator, @strepanier03, @jasperhuangg, @stitesExpensify, @roryabraham Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@strepanier03 can we get this paid out so that we can close the issue please? 😄 |
Sure thing @stitesExpensify - I had a question about payment that's resolved now, and it's my Monday so I'm only just getting back online from the weekend. |
@gadhiyamanan - I've hired you to the job, please accept as soon as you can and I'll keep an eye out for it so I can pay. |
@strepanier03 offer accepted, thanks! |
Thank you @gadhiyamanan - I've paid you via Upwork and closed the contract. Closing this now. |
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:
Top bar color should not be different
Actual Result:
Top bar color is different
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.74.4
Reproducible in staging?: y
Reproducible in production?: n
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
RPReplay_Final1695724253.MP4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695724265178069
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: