Skip to content

[HOLD for payment 2024-03-22] [$500] Authorized payer - Enter key does not select another member as authorized payer #38203

Closed

Description

@kavimuru

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.51-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: applause internal team
Slack conversation:

Action Performed:

Precondition:

  • User is an owner of Collect workspace.
  • There is at least another admin in the workspace.
  1. Go to staging.new.expensify.com.
  2. Go to workspace settings > Collect workspace.
  3. Go to Workflows.
  4. Enable Make or track payments if not enabled.
  5. Click Authorized payer.
  6. Navigate to another admin via keyboard and hit Enter.

Expected Result:

Enter key will select another admin as the authorized payer.

Actual Result:

Enter key is not responsive when the selection is on another admin.
When the selection is on the authorized payer, Enter key exits the RHP.

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

Bug6411925_1710308620444.bandicam_2024-03-13_13-39-04-261.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01cb6806f250da1d85
  • Upwork Job ID: 1767835771147452416
  • Last Price Increase: 2024-03-13
  • Automatic offers:
    • jjcoffee | Contributor | 0
    • ishpaul777 | Contributor | 0

Activity

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

    @melvin-bot

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

  3. github-actions commented on Mar 13, 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.
  4. melvin-bot commented on Mar 13, 2024

    @melvin-bot

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

  5. kavimuru commented on Mar 13, 2024

    @kavimuru
    Author

    @Beamanator FYI 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.

  6. 30 remaining items

  7. jjcoffee commented on Mar 20, 2024

    @jjcoffee
    Contributor
    • The PR that introduced the bug has been identified. Link to the PR: feat: Workflow payer page #37629
    • 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: https://github.com/Expensify/App/pull/37629/files#r1531725204
    • 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: N/A
    • Determine if we should create a regression test for this bug. Yes
    • 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.

    Regression Test Proposal

    1. Go to Workspace settings > Collect workspace.
    2. Go to Workflows.
    3. Enable Make or track payments if not enabled.
    4. Click Authorized payer.
    5. Navigate to another admin via keyboard and hit Enter, verify currect user is Selected as authoirized payer

    Do we agree 👍 or 👎

  8. luacmartins commented on Mar 20, 2024

    @luacmartins
    Contributor

    We'll add regression steps once this feature is fully implemented.

  9. jjcoffee commented on Mar 25, 2024

    @jjcoffee
    Contributor

    @lschurr Friendly bump for payment! 🙇

  10. lschurr commented on Mar 25, 2024

    @lschurr
    Contributor

    All set! Payment for $500 sent via Upwork to @jjcoffee

  11. ishpaul777 commented on Mar 25, 2024

    @ishpaul777
    Contributor

    Actually this was a follow up PR, is this eligible for payment @luacmartins

  12. lschurr commented on Mar 25, 2024

    @lschurr
    Contributor

    Ah it looks like this GH wasn't assigned to you so that's why the offer didn't go out @ishpaul777

  13. melvin-bot commented on Mar 25, 2024

    @melvin-bot

    📣 @ishpaul777 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  14. added and removed on Mar 25, 2024
  15. lschurr commented on Mar 25, 2024

    @lschurr
    Contributor

    Payment summary:

  16. ishpaul777 commented on Mar 25, 2024

    @ishpaul777
    Contributor

    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