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

[HOLD for payment 2024-07-17] [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences #44178

Closed
1 of 6 tasks
lanitochka17 opened this issue Jun 21, 2024 · 28 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 External Added to denote the issue can be worked on by a contributor NewFeature Something to build that is a new item.

Comments

@lanitochka17
Copy link

lanitochka17 commented Jun 21, 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.0.0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause -Internal Team

Issue found when executing PR #43543

Action Performed:

  1. Go to staging.new.expensify.com
  2. Press CMD + D

Expected Result:

Troubleshoot modal opened from shortcut will be complete

Actual Result:

Troubleshoot modal opened from shortcut is missing Testing preferences

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

Bug6520668_1718987164941.20240622_002210.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a41f20c0677b7543
  • Upwork Job ID: 1805670065479684749
  • Last Price Increase: 2024-06-25
  • Automatic offers:
    • allgandalf | Reviewer | 102915241
    • aeioual | Contributor | 102915244
Issue OwnerCurrent Issue Owner: @anmurali
@lanitochka17 lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jun 21, 2024
Copy link

melvin-bot bot commented Jun 21, 2024

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

@lanitochka17
Copy link
Author

@anmurali 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

@nyomanjyotisa
Copy link
Contributor

nyomanjyotisa commented Jun 22, 2024

Proposal

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

Troubleshoot modal opened from shortcut is missing Testing preferences

What is the root cause of that problem?

The Testing preference on troubleshoot modal is only displayed if the environment is Development

{isDevelopment && <TestToolMenu />}

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

Make the Testing preference on troubleshoot displayed if the environment is not Production, so it will be displayed on Development and Staging environment

image

What alternative solutions did you explore? (Optional)

Create a reusable component to display a list of troubleshooting configurations. This component will ensure that both the Troubleshoot modal and the Troubleshoot page consistently display the same configurations. It will also simplify the process of adding or modifying configurations in the future if needed.

Result:
https://github.com/Expensify/App/assets/73281575/e07b738a-ac78-4f09-98d1-e8e85bc28e2a

@aeioual
Copy link
Contributor

aeioual commented Jun 22, 2024

Proposal

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

Troubleshoot modal opened from shortcut is missing Testing preferences

What is the root cause of that problem?

We do not allow the testtoolMenu on staging, hence we do not see the options.

{isDevelopment && <TestToolMenu />}

I also found one more bug, the order of options is not right, we should first display the Logs options and then the TestToolMenu (We do the same with the troubleshoot page too):
Screenshot 2024-06-23 at 12 30 52 AM

As you can see the first option is of client side logging then the testing preference, we should maintain this order in shortcut too.

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

  • Change the check to !isProduction from the following hook>
    isProduction: environment === CONST.ENVIRONMENT.PRODUCTION,
  • Then we should move the code block after the following line to match the UI with the troubleshoot page:

</TestToolRow>
)}

</TestToolRow>
                )}
                {!isProduction && <TestToolMenu />}

What alternative solutions did you explore? (Optional)

@melvin-bot melvin-bot bot added the Overdue label Jun 24, 2024
Copy link

melvin-bot bot commented Jun 25, 2024

@anmurali Whoops! This issue is 2 days overdue. Let's get this updated quick!

@anmurali anmurali added the External Added to denote the issue can be worked on by a contributor label Jun 25, 2024
@melvin-bot melvin-bot bot changed the title Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences Jun 25, 2024
Copy link

melvin-bot bot commented Jun 25, 2024

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

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jun 25, 2024
Copy link

melvin-bot bot commented Jun 25, 2024

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

@anmurali
Copy link

Trying to figure out where this issue goes and I don't think any of the roadmap projects make sense. It is about testing, and so quality perhaps?

@nyomanjyotisa
Copy link
Contributor

Updating proposal , adding alternative solution

@allgandalf
Copy link
Contributor

thanks for your proposals everyone!

Both contributors have correct RCA.

Lets go with @aeioual's proposal here, that bug that they found out is important here considering the consistency between options.

🎀👀🎀 C+ reviewed

Also want to confirm the @Expensify/design opinion once, the troubleshoot shortcut modal options should be consistent with the troubleshoot page options right?

  • Currently on troubleshoot page, we first show:
  1. Client side logging
  2. Testing preferences

After this PR, we should follow the same order in the troubleshoot shortcut modal right?

Copy link

melvin-bot bot commented Jun 26, 2024

Triggered auto assignment to @bondydaa, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@shawnborton
Copy link
Contributor

That sounds correct to me? I'm not too sure but it does seem to make sense that the page and the modal would be consistent.

@muttmuure
Copy link
Contributor

The idea behind the modal was to mirror the "four finger tap" options that you have on mobile - adding more options to the modal would be a new feature, not a bug. #43256

@muttmuure muttmuure added NewFeature Something to build that is a new item. and removed Bug Something is broken. Auto assigns a BugZero manager. labels Jun 27, 2024
Copy link

melvin-bot bot commented Jun 27, 2024

Current assignee @anmurali is eligible for the NewFeature assigner, not assigning anyone new.

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Daily KSv2 labels Jun 27, 2024
@muttmuure muttmuure moved this to MEDIUM in [#whatsnext] #quality Jun 27, 2024
@allgandalf
Copy link
Contributor

Automation Failed ⚠️ , this was deployed to production 2 days ago!

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Jul 10, 2024
@melvin-bot melvin-bot bot changed the title [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences [HOLD for payment 2024-07-17] [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences Jul 10, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Jul 10, 2024
Copy link

melvin-bot bot commented Jul 10, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Jul 10, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 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-07-17. 🎊

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

Copy link

melvin-bot bot commented Jul 10, 2024

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • [@allgandalf] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@anmurali] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Jul 15, 2024
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2024-07-17] [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences [HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences Jul 15, 2024
Copy link

melvin-bot bot commented Jul 15, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.6-8 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-07-22. 🎊

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

Copy link

melvin-bot bot commented Jul 15, 2024

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • [@allgandalf] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@anmurali] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

@allgandalf
Copy link
Contributor

Regression Test Proposal

Note: Can only test on Desktop/MacOS Web:

  1. Open App
  2. Press CMD + D

Verify that the Troubleshoot modal opens up

Do we agree 👍 or 👎

@allgandalf
Copy link
Contributor

Note

@anmurali , this is already ready for payment, melvin really is acting weird, the actual date for payment was 15th

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed Weekly KSv2 labels Jul 16, 2024
@bondydaa bondydaa changed the title [HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences [HOLD for payment 2024-07-17] [$250] Troubleshoot - Troubleshoot modal opened from shortcut is missing Testing preferences Jul 18, 2024
@allgandalf
Copy link
Contributor

Waiting for payment!

Copy link

melvin-bot bot commented Jul 19, 2024

@bondydaa, @anmurali, @allgandalf, @aeioual Whoops! This issue is 2 days overdue. Let's get this updated quick!

@allgandalf
Copy link
Contributor

This issue can be closed, payment has been completed

@melvin-bot melvin-bot bot removed the Overdue label Jul 22, 2024
@github-project-automation github-project-automation bot moved this from MEDIUM to Done in [#whatsnext] #quality Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 External Added to denote the issue can be worked on by a contributor NewFeature Something to build that is a new item.
Projects
Status: Done
Development

No branches or pull requests

8 participants