Skip to content

[HOLD for payment 2024-11-29] [$250] Search - The shortcut CTRL + K does not work with a user as employee in a WS #52260

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: 9.0.59-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5191872
Issue reported by: Applause - Internal Team

Action Performed:

  1. Sign in to the app with a new Gmail account
  2. Choose "Get paid back by my employer" from the onboarding tasks
  3. Type a Name and Last name and click the "Continue" button
  4. Go to Settings, create a new workspace and invite a new account as an employee
  5. Log in with the new employee's account in incognito mode
  6. Press the shortcut CTRL + K to open search dialog

Expected Result:

The shortcut CTRL + K to open the search dialog should open correctly

Actual Result:

Pressing the combination CTRL + K to open the search dialog does not execute, while the other shortcuts such as CTRL + J and CTRL + D work correctly

Workaround:

Unknown

Platforms:

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

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6658921_1731075276789.Ctrl___k_doesn_t_Work.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021854902169710515284
  • Upwork Job ID: 1854902169710515284
  • Last Price Increase: 2024-11-13
  • Automatic offers:
    • dukenv0307 | Contributor | 104806147
    • truph01 | Contributor | 104867213
Issue OwnerCurrent Issue Owner: @abekkala

Activity

  1. melvin-bot commented on Nov 8, 2024

    @melvin-bot

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

  2. melvin-bot commented on Nov 8, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Nov 8, 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. mountiny commented on Nov 8, 2024

    @mountiny
    Contributor

    I ran into this problem in production already cc @daledah I believe someone pointed to your PR here #51547 any chance you could have a look?

  5. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 8, 2024
  6. melvin-bot commented on Nov 8, 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.

  7. daledah commented on Nov 8, 2024

    @daledah
    Contributor

    @mountiny I want to confirm this: If an account is created optimistically by another user (for this issue, the account is created by search), then when logging in, this account will not have to go through onboarding steps. Is that correct?

  8. 89 remaining items

  9. melvin-bot commented on Nov 22, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.65-5 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-11-29. 🎊

    For reference, here are some details about the assignees on this issue:

  10. melvin-bot commented on Nov 22, 2024

    @melvin-bot

    @dukenv0307 @abekkala @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  11. dukenv0307 commented on Nov 25, 2024

    @dukenv0307
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: The offending PR is reverted, we use the new approach

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. Yes

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Log in with any account in incognito mode
    2. Turn on console and type: Onyx.set('nvp_onboarding', '{"selfTourViewed": true}');
    3. Press the shortcut CTRL + K to open search dialog
    4. Verify he shortcut CTRL + K to open the search dialog should open correctly

    Do we agree 👍 or 👎

  12. mountiny commented on Nov 25, 2024

    @mountiny
    Contributor

    I am not sure if we need such test

  13. abekkala commented on Nov 26, 2024

    @abekkala
    Contributor

    PAYMENT SUMMARY FOR NOV 29

  14. abekkala commented on Nov 29, 2024

    @abekkala
    Contributor

    @truph01 payment sent and contract ended - thank you! 🎉

  15. abekkala commented on Nov 29, 2024

    @abekkala
    Contributor

    @dukenv0307 waiting for acceptance of offer in Upwork - thanks!

  16. dukenv0307 commented on Dec 1, 2024

    @dukenv0307
    Contributor

    @abekkala I have requested ND payment. The Upwork offer is not needed. Thanks!

  17. abekkala commented on Dec 2, 2024

    @abekkala
    Contributor

    @dukenv0307 Ah ok, I see you were just added to NewDot payments on Nov 19. (But the auto offer was sent still by melvin)

    thanks!


    PAYMENT SUMMARY

  18. JmillsExpensify commented on Dec 5, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @dukenv0307

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