search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.58k stars 2.92k forks source link

[Supportal] Make Supportal debug console mirror user's console #51632

Open stephanieelliott opened 4 weeks ago

stephanieelliott commented 4 weeks ago

Context:

To help support customers in New Expensify, we need to ensure that when Supportaled into customer accounts, the debug tools, including Onyx data, show the actual data the user would see. This would help us diagnose RBR/GBR/unread errors we see.

Version Number: Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): manager.stephanie@expensicorp.com Logs: N/A Expensify/Expensify Issue URL: N/A Issue reported by: @stephanieelliott / @danielrvidal Slack conversation: https://expensify.slack.com/archives/C07NZ8B1VTQ/p1728500635598069

Action Performed:

  1. In browser A, Support log into a test account
  2. In browser B, directly log into the same test account
  3. In both browsers (A and B), navigate to Settings > Troubleshoot > View Debug Console

Expected Result:

Note: this is an improvement, not a regression Debug console should be the same in browsers A and B

Actual Result:

Debug console in browsers A and B is not the same

Workaround:

N/A

Platforms:

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

Screenshots/Videos

image

Example:

Supportal data

Direct login data

melvin-bot[bot] commented 4 weeks ago

Triggered auto assignment to @RachCHopkins (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

melvin-bot[bot] commented 4 weeks ago

:warning: It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time :warning:

melvin-bot[bot] commented 4 weeks ago

Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

dannymcclain commented 4 weeks ago

Doesn't seem like this actually needs any design support—mostly just code wizardry yeah? 🧙

RachCHopkins commented 2 weeks ago

@maddylewis should I add the hot picks label to this?

youssef-lr commented 1 week ago

@stephanieelliott @danielrvidal have we confirmed this is an issue? Because I think Onyx logs will just print whatever the app has done and it should technically be the same. Have we confirmed that by taking Action A, different logs were printed in Supportal vs login? if not I can conduct this test.

RachCHopkins commented 1 week ago

@youssef-lr I think it's worth testing that - I'm happy to help, if you can spoon-feed me some instructions!

stephanieelliott commented 1 week ago

@youssef-lr this has been tested per the Action Performed steps — see the end of the issue body for the result!

  1. In browser A, Support log into a test account
  2. In browser B, directly log into the same test account
  3. In both browsers (A and B), navigate to Settings > Troubleshoot > View Debug Console

The problem is that the information displayed in the debug console when direct logged in differs from what shows when support logged in.

image

There are attached logs for for each login (supportal vs direct), as well as a TXT file of the Onyx logs for each login.

Supportal data

Direct login data