You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-08-26] Workspace switcher - Huge gap between "Create a workspace" modal and "Workspaces" title #47601
Version Number: v9.0.21-3 Reproducible in staging?: Y Reproducible in production?: N Email or phone of affected tester (no customers):applausetester+kh050806@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Account has no workspace.
Go to staging.new.expensify.com
Open workspace switcher.
Expected Result:
"Create a workspace" modal should be right below the "Workspaces" title (production behavior).
Actual Result:
There is huge gap between "Create a workspace" modal and "Workspaces" title.
👋 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:
Identify the pull request that introduced this issue and revert it.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.21-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@luacmartins] The PR that introduced the bug has been identified. Link to the PR:
[@luacmartins] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@luacmartins] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@wildan-m] Determine if we should create a regression test for this bug.
[@wildan-m] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@abekkala] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Aug 17, 2024
Triggered auto assignment to @luacmartins (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 17, 2024
Triggered auto assignment to @abekkala (
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.github-actions commentedon Aug 17, 2024
👋 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:
IuliiaHerets commentedon Aug 17, 2024
We think that this bug might be related to #vip-vsb
etCoderDysto commentedon Aug 17, 2024
It might be caused by #47527
wildan-m commentedon Aug 18, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
The logic in this render might be incorrect:
App/src/components/SelectionList/BaseSelectionList.tsx
Lines 690 to 695 in 62722e8
headerMessage value should be mandatory to show the component
What changes do you think we should make in order to solve the problem?
Change the logic to
What alternative solutions did you explore? (Optional)
N/A
luacmartins commentedon Aug 19, 2024
@wildan-m are you available to work on a fix?
21 remaining items
melvin-bot commentedon Aug 19, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 19, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.21-4 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 2024-08-26. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 19, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
wildan-m commentedon Aug 27, 2024
I think we don't need to create regression test, it's not directly related to any flow
Is "Needs manual offer from BZ" a payment method? Can I receive payment through UpWork instead?
wildan-m commentedon Sep 3, 2024
@luacmartins @abekkala bump for payment
wildan-m commentedon Sep 6, 2024
@luacmartins bump #47601 (comment)
luacmartins commentedon Sep 6, 2024
Seems like I closed this issue without payment 😬 Reopening so we can process it @abekkala
abekkala commentedon Sep 6, 2024
PAYMENT SUMMARY
wildan-m commentedon Sep 6, 2024
@abekkala thanks, accepted the offer
abekkala commentedon Sep 6, 2024
@wildan-m payment sent and contract ended - thank you! 🎉