Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[$250] [Search v2.3] - Current name is not populated in the name field and it is not auto-focused #49207

Closed
6 tasks done
IuliiaHerets opened this issue Sep 14, 2024 · 25 comments
Closed
6 tasks done
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2

Comments

@IuliiaHerets
Copy link

IuliiaHerets commented Sep 14, 2024

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.35-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Issue was found when executing this PR: #48566
Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

  • User has saved a few searches.
  1. Go to staging.new.expensify.com
  2. Go to Search.
  3. Click 3-dot menu next to a saved search > Rename.
  4. Save a custom name.
  5. Click 3-dot menu next to the same saved search > Rename.

Expected Result:

The current name will be populated in the name field and it will auto-focused.

Actual Result:

The current name is not populated in the name field and it is not auto-focused.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6603105_1726282008408.20240914_104412.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @jayeshmangwani
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021836684527709552516
  • Upwork Job ID: 1836684527709552516
  • Last Price Increase: 2024-09-19
  • Automatic offers:
    • Nodebrute | Contributor | 104051960
@IuliiaHerets IuliiaHerets added DeployBlockerCash This issue or pull request should block deployment Bug Something is broken. Auto assigns a BugZero manager. labels Sep 14, 2024
Copy link
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.

Copy link

melvin-bot bot commented Sep 14, 2024

Triggered auto assignment to @slafortune (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.

Copy link

melvin-bot bot commented Sep 14, 2024

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

@Nodebrute
Copy link
Contributor

Nodebrute commented Sep 14, 2024

Proposal

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

Current name is not populated in the name field and it is not auto-focused

What is the root cause of that problem?

We are not autofocusing this field and we are also not adding defaultValue

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

We can add const {inputCallbackRef} = useAutoFocusInput(); and then pass it here
We can also pass defaultValue={name}
Optional: we can also pass value prop

What alternative solutions did you explore? (Optional)

@srikarparsi
Copy link
Contributor

Hi @lakchote or @luacmartins, do you think you could take a look at this whenever you have a chance? I think this comes from this PR

@srikarparsi
Copy link
Contributor

I think the auto-focussed part has been reported here

@luacmartins
Copy link
Contributor

This is known and NAB. We're addressing it in a follow up

@luacmartins luacmartins removed the DeployBlockerCash This issue or pull request should block deployment label Sep 15, 2024
@melvin-bot melvin-bot bot added the Overdue label Sep 18, 2024
@luacmartins luacmartins changed the title Saved search - Current name is not populated in the name field and it is not auto-focused [Search v2.3] - Current name is not populated in the name field and it is not auto-focused Sep 19, 2024
@lakchote lakchote added the External Added to denote the issue can be worked on by a contributor label Sep 19, 2024
@melvin-bot melvin-bot bot changed the title [Search v2.3] - Current name is not populated in the name field and it is not auto-focused [$250] [Search v2.3] - Current name is not populated in the name field and it is not auto-focused Sep 19, 2024
Copy link

melvin-bot bot commented Sep 19, 2024

Job added to Upwork: https://www.upwork.com/jobs/~021836684527709552516

Copy link

melvin-bot bot commented Sep 19, 2024

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

@melvin-bot melvin-bot bot removed the Overdue label Sep 19, 2024
@jayeshmangwani
Copy link
Contributor

We're addressing it in a follow up

@luacmartins @lakchote If we're going to address this in a follow-up, should we close the issue or assign it to the person who will tackle it?

@lakchote
Copy link
Contributor

@jayeshmangwani I'd like you to review Nodebrute's proposal here.

Then I'll assign, if the proposal sounds good.

@jayeshmangwani
Copy link
Contributor

@lakchote We can go with @Nodebrute's Proposal. Adding the inputCallbackRef to the ref of the InputWrapper and setting the defaultValue looks good.

@QasimBham
Copy link

Proposal
Please re-state the problem that we are trying to solve in this issue.
Current name is not populated in the name field and it is not auto-focused

What is the root cause of that problem?
We are not autofocusing this field and we are also not adding defaultValue

What changes do you think we should make in order to solve the problem?
We can use the state management for this. We can use the defaultValue = {name}. Other than this we can use the default state set to {name}.
Optional: we can also pass value prop

What alternative solutions did you explore? (Optional)

Copy link
Contributor

githubUser Your proposal will be dismissed because you did not follow the proposal template.

@jayeshmangwani
Copy link
Contributor

@lakchote Nodebrute's proposal looks good to me. What do you think?

@lakchote
Copy link
Contributor

@Nodebrute's proposal LGTM.

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Sep 20, 2024
Copy link

melvin-bot bot commented Sep 20, 2024

📣 @Nodebrute 🎉 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 📖

@Nodebrute
Copy link
Contributor

I’ll raise a PR in a few hours.

@Nodebrute Nodebrute mentioned this issue Sep 20, 2024
50 tasks
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Sep 20, 2024
@luacmartins luacmartins moved this from Polish to Done in [#whatsnext] #expense Sep 23, 2024
@slafortune
Copy link
Contributor

not deployed yet

Copy link

melvin-bot bot commented Sep 25, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@Nodebrute
Copy link
Contributor

^ False positive my PR didn't cause the issue mentioned in #49739. The change we made was simple, involving autofocus and setting a default value for the field.

The root cause of the other issue was this PR, where we introduced the title variable but forgot to pass it to the navigation function see #49235 (comment)

@jayeshmangwani
Copy link
Contributor

@slafortune PR has been in production for 2 weeks, and it's now ready for payment.

@slafortune
Copy link
Contributor

slafortune commented Oct 9, 2024

@jayeshmangwani - Role C+ - is due $250 via New Dot
@Nodebrute - Role Contributor - Paid $250 via Upworks

@jayeshmangwani
Copy link
Contributor

@slafortune Please update the summary, I am not an Expert Contributor; I am a C+.

@garrettmknight
Copy link
Contributor

$250 approved for @jayeshmangwani

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2
Projects
Status: Done
Development

No branches or pull requests

9 participants