-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Supportal] Workspace expense does not load when clicked #50627
Comments
Triggered auto assignment to @dylanexpensify ( |
@dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@dylanexpensify Huh... This is 4 days overdue. Who can take care of this? |
Tackling this evening! |
Triggered auto assignment to @mallenexpensify ( |
Hey @mallenexpensify! I'm heading out on parental leave so reassigning this! TY! 🙇♂️ |
@stephanieelliott what should BZ do with supportal-related issues? I can update the team and add deets to What do I do when assigned a BugZero (Bug0) chore via the Bug label auto assigner? |
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@stephanieelliott 👀 above plz. assigned to you and made you owner for a min |
Ah thanks for the bump @mallenexpensify! I'm thinking we just treat these as normal Are you thinking there are some other nuances that need to be documented for these? |
Chatting with Steph about |
Triggered auto assignment to @Christinadobrzyn ( |
@Christinadobrzyn I'm off the next week, can you please keep an eye on this issue til I'm back? Thx. We're waiting for someone internal to pick up. |
sounds good! monitoring! |
This comment was marked as off-topic.
This comment was marked as off-topic.
update for Melvin - we're testing this! |
I just tested again and this is still happening - I'm getting a 2024-11-13_10-55-58.mp4Tested when supportaling into [email protected] |
Tested the fix and it seems to work fine for me locally. It's in review. |
Amazing! Thank you so much @chiragsalian! Updated Canvas about this status |
TY! Testing again:
Logs for supportaling into [email protected] I can't find any other logs but it looks like this is still happening (sorry) @chiragsalian |
Weird, from the logs and the db it says those reports are not shared with [email protected]. I'm not exactly sure how the person sees those reports in Search and how OpenReport is supposed to work for them. Shall ask in engg-chat. |
Thanks @chiragsalian! Let me know if there's anything I can do to help test this. |
@chiragsalian, @mallenexpensify, @Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Investigated with @luacmartins today and we found the source of the issue. While we believe we found the solution testing that will be a bit tricky to ensure nothing is broken. I'm a bit swamped so i don't think i can get to it this week and plus i don't think its a daily so I'll demote it to weekly. Aiming to tackle maybe next week. If you feel the priority is different let me know. |
Awesome thank you @chiragsalian! |
Hi @chiragsalian just checking on any update on this one! TY! |
Sorry, i haven't looked into it yet due to other higher priorities. |
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): [email protected]
Logs: LOGS
Expensify/Expensify Issue URL: N/A
Issue reported by: @stephanieelliott
Slack conversation: https://expensify.slack.com/archives/C07NZ8B1VTQ/p1728500635598069
Action Performed:
Expected Result:
Expense thread should open with a link to workspace chat at the top (see right side of screen in video)
Actual Result:
Page shows endless loading, expense does not load.
Workaround:
None, this is problematic because it's currently the workaround for us to view workspace chats
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
2024-10-10_22-08-22.mp4
Issue Owner
Current Issue Owner: @chiragsalianIssue Owner
Current Issue Owner: @chiragsalianThe text was updated successfully, but these errors were encountered: