Skip to content

[HOLD for payment 2024-05-09] [$500] Hold Request - "Hold" banner is aligned to the top when there is scan request message #37536

Closed

Description

@lanitochka17

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: 1.4.45-1
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to 1:1 DM
  3. Create a scan request
  4. Go to request details page
  5. Click 3-dot menu > Hold request
  6. Add a reason and save it

Expected Result:

The "Hold" banner will be aligned in the middle of the given space

Actual Result:

The "Hold" banner is aligned to the top of the given space when there is scan request message

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6397350_1709227408773.20240229_234646.mp4
Bug6397350_1709227408781!Screenshot_2024-03-01_at_01 12 12

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01dd5d1b7c81a77704
  • Upwork Job ID: 1763306586849918976
  • Last Price Increase: 2024-03-07
  • Automatic offers:
    • neonbhai | Contributor | 0
Issue OwnerCurrent Issue Owner: @isabelastisser

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 29, 2024
  2. melvin-bot commented on Feb 29, 2024

    @melvin-bot

    Triggered auto assignment to @isabelastisser (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. lanitochka17 commented on Feb 29, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave7
    CC @RachCHopkins

  4. lanitochka17 commented on Feb 29, 2024

    @lanitochka17
    Author

    @isabelastisser I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  5. gijoe0295 commented on Feb 29, 2024

    @gijoe0295
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    "Hold" banner is aligned to the top when there is scan request message

    What is the root cause of that problem?

    We only have bottom padding for hold banner as per here. It only works when there's only it and no other banners (money request status bar) above.

    What changes do you think we should make in order to solve the problem?

    Add a prop shouldShowPaddingTop to HoldBanner. This check will be true when there's any other status bar above (e.g., MoneyRequestHeaderStatusBar).

    <HoldBanner shouldShowPaddingTop={isPending || isScanning} />

    In that case, we use styles.pv3 for the HoldBanner. Otherwise, only use pb3.

    What alternative solutions did you explore? (Optional)

    NA

  6. isabelastisser commented on Feb 29, 2024

    @isabelastisser
    Contributor

    @lanitochka17 I agree that this can barely be noticed. I raised it for discussion in Slack.

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 29, 2024
  8. changed the title [-] Hold Request - "Hold" banner is aligned to the top when there is scan request message[/-] [+][$500] Hold Request - "Hold" banner is aligned to the top when there is scan request message[/+] on Feb 29, 2024
  9. melvin-bot commented on Feb 29, 2024

    @melvin-bot
  10. melvin-bot commented on Feb 29, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (External)

  11. 86 remaining items

  12. isabelastisser commented on May 16, 2024

    @isabelastisser
    Contributor
  13. Santhosh-Sellavel commented on May 16, 2024

    @Santhosh-Sellavel
    Collaborator

    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:

  14. melvin-bot commented on May 16, 2024

    @melvin-bot

    @francoisl, @dragnoir, @isabelastisser, @neonbhai, @Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick!

  15. francoisl commented on May 16, 2024

    @francoisl
    Contributor

    Works for me. @isabelastisser feel free to process the payments and close the issue. Thanks!

  16. neonbhai commented on May 16, 2024

    @neonbhai
    Contributor

    Noting that the PR was reviewed by me here but seems like the automation didn't mention it. Please take a look 🙇

    cc: @isabelastisser

  17. dragnoir commented on May 17, 2024

    @dragnoir
    Contributor

    @isabelastisser pls consider this when payment #37536 (comment)

    Thank you

  18. isabelastisser commented on May 17, 2024

    @isabelastisser
    Contributor

    Based on @shawnborton's comment here, I'm increasing the payment to @dragnoir to $750.

    Payments summary:

    @dragnoir requires payment $750 (manual offer https://www.upwork.com/nx/wm/offer/102358820)
    @neonbhai requires payment automatic offer (Contributor) $750
    @Santhosh-Sellavel requires payment through NewDot Manual Requests $500 PENDING

  19. isabelastisser commented on May 17, 2024

    @isabelastisser
    Contributor

    All set!

  20. dragnoir commented on May 17, 2024

    @dragnoir
    Contributor

    @isabelastisser offer accepted. Thank you

  21. neonbhai commented on May 17, 2024

    @neonbhai
    Contributor

    @isabelastisser hi, the original job was split with me and @dragnoir. As noted here #37536 (comment)

    I also ended up reviewing one of the linked PRs, so the payout would be $250 + $500 for me! Please take a look 🙇

  22. Santhosh-Sellavel commented on May 22, 2024

    @Santhosh-Sellavel
    Collaborator

    Requested on ND

  23. JmillsExpensify commented on May 31, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @Santhosh-Sellavel

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.DailyKSv2ExternalAdded 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