Skip to content

[$500] Tag - No search field when there are more than 9 tags in the tag list #36859

Closed

Description

@izarutskaya

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


Found when validating PR : #35541

Version Number: v1.4.43-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation:

Action Performed:

Precondition:

  • User is an employee of Collect workspace.
  • The Collect workspace has more than 9 tags.
  1. Navigate to staging.new.expensify.com
  2. Go to workspace chat.
  3. Click + > Request money > Manual.
  4. Enter amount > Next.
  5. Click Show more.
  6. Click Tag.

Expected Result:

There will be a search field above tag list because there are more than 9 tags.

Actual Result:

There is no search field above tag list when there are more than 9 tags.

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

Bug6385312_1708402897997.bandicam_2024-02-20_08-50-11-856.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~014ce6942105099a0b
  • Upwork Job ID: 1759888738434629632
  • Last Price Increase: 2024-02-20

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 20, 2024
  2. changed the title [-]Tag - No search field when there are more than 9 tags in the tag list[/-] [+][$500] Tag - No search field when there are more than 9 tags in the tag list[/+] on Feb 20, 2024
  3. melvin-bot commented on Feb 20, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 20, 2024
  5. melvin-bot commented on Feb 20, 2024

    @melvin-bot

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

  6. melvin-bot commented on Feb 20, 2024

    @melvin-bot

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

  7. github-actions commented on Feb 20, 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.
  8. 22 remaining items

  9. Beamanator commented on Feb 22, 2024

    @Beamanator
    Contributor

    Removing deploy blocker label since fix is now in staging

  10. rezkiy37 commented on Feb 22, 2024

    @rezkiy37
    Contributor

    ...I think it's only worth a payout if @rezkiy37 used your proposed solution to guide his fix

    Yeah, the proposal helped me to fix the bug.

  11. Beamanator commented on Feb 22, 2024

    @Beamanator
    Contributor

    Noice, then ya i think it does make sense for @tienifr to get some bonus for the help - cc @kevinksullivan , the payment pro in this issue

  12. kevinksullivan commented on Feb 22, 2024

    @kevinksullivan
    Contributor

    Just to clarify, @tienifr should be getting paid the same as others for the help, or a fractional "bonus"?

  13. tienifr commented on Feb 29, 2024

    @tienifr
    Contributor

    @Beamanator Can you check the question above ^? Thanks

  14. kevinksullivan commented on Mar 1, 2024

    @kevinksullivan
    Contributor

    Payout summary:

    @tienifr offer sent, let me know when you accept.

  15. tienifr commented on Mar 2, 2024

    @tienifr
    Contributor

    @kevinksullivan I accepted, thanks!

  16. JmillsExpensify commented on Mar 12, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @allroundexperts based on summary.

  17. tienifr commented on Apr 1, 2024

    @tienifr
    Contributor

    @tienifr $125 (bonus for assisting with proposal)

    @kevinksullivan Could you help with payment here? Thanks!

  18. melvin-bot commented on Apr 5, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @Beamanator, @kevinksullivan, @allroundexperts, @rezkiy37 eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  19. kevinksullivan commented on Apr 10, 2024

    @kevinksullivan
    Contributor

    all set

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions