Skip to content

[HOLD for payment 2024-08-26] Workspace switcher - Huge gap between "Create a workspace" modal and "Workspaces" title #47601

Closed

Description

@IuliiaHerets

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


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.
  1. Go to staging.new.expensify.com
  2. 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.

Workaround:

Unknown

Platforms:

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6574871_1723923186190!Screenshot_2024-08-18_at_03 30 12

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @wildan-m

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 17, 2024
  2. melvin-bot commented on Aug 17, 2024

    @melvin-bot

    Triggered auto assignment to @luacmartins (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Aug 17, 2024

    @melvin-bot

    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.

  4. github-actions commented on Aug 17, 2024

    @github-actions
    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.
  5. IuliiaHerets commented on Aug 17, 2024

    @IuliiaHerets
    Author

    We think that this bug might be related to #vip-vsb

  6. etCoderDysto commented on Aug 17, 2024

    @etCoderDysto
    Contributor

    It might be caused by #47527

  7. wildan-m commented on Aug 18, 2024

    @wildan-m
    Contributor

    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:

    {(((!isLoadingNewOptions || headerMessage !== translate('common.noResultsFound')) && !!headerMessage) ||
    (flattenedSections.allOptions.length === 0 && !showLoadingPlaceholder)) && (
    <View style={headerMessageStyle ?? [styles.ph5, styles.pb5]}>
    <Text style={[styles.textLabel, styles.colorMuted, styles.minHeight5]}>{headerMessage}</Text>
    </View>
    )}

    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

    {(
        ((!isLoadingNewOptions || headerMessage !== translate('common.noResultsFound')) ||
        (flattenedSections.allOptions.length === 0 && !showLoadingPlaceholder)) &&
        !!headerMessage
    ) && (
        <View style={headerMessageStyle ?? [styles.ph5, styles.pb5]}>
            <Text style={[styles.textLabel, styles.colorMuted, styles.minHeight5]}>
                {headerMessage}
            </Text>
        </View>
    )}

    What alternative solutions did you explore? (Optional)

    N/A

  8. luacmartins commented on Aug 19, 2024

    @luacmartins
    Contributor

    @wildan-m are you available to work on a fix?

  9. 21 remaining items

  10. melvin-bot commented on Aug 19, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Aug 19, 2024

    @melvin-bot

    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:

    • @wildan-m requires payment (Needs manual offer from BZ)
  12. melvin-bot commented on Aug 19, 2024

    @melvin-bot

    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:
  13. wildan-m commented on Aug 27, 2024

    @wildan-m
    Contributor

    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?

  14. wildan-m commented on Sep 3, 2024

    @wildan-m
    Contributor

    @luacmartins @abekkala bump for payment

  15. wildan-m commented on Sep 6, 2024

    @wildan-m
    Contributor
  16. luacmartins commented on Sep 6, 2024

    @luacmartins
    Contributor

    Seems like I closed this issue without payment 😬 Reopening so we can process it @abekkala

  17. abekkala commented on Sep 6, 2024

    @abekkala
    Contributor

    PAYMENT SUMMARY

  18. wildan-m commented on Sep 6, 2024

    @wildan-m
    Contributor

    @abekkala thanks, accepted the offer

  19. abekkala commented on Sep 6, 2024

    @abekkala
    Contributor

    @wildan-m payment sent and contract ended - thank you! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions