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

Unable to access an expense report after having used the Expensify Card #53855

Open
1 of 8 tasks
m-natarajan opened this issue Dec 10, 2024 · 5 comments
Open
1 of 8 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Internal Requires API changes or must be handled by Expensify staff Needs Reproduction Reproducible steps needed

Comments

@m-natarajan
Copy link

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @lakchote
Slack conversation (hyperlinked to channel name): #expensify bugs

Action Performed:

  1. Pay with the Expensify Card a snack expense
  2. Go to the member's workspace related to contractors
  3. Click on the expense to assign the correct expense category

Expected Result:

The user should be able to access the expense without any errors

Actual Result:

The user can't access the report, and the report ID in the URL is -1.

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
Screen.Recording.2024-12-10.at.09.59.16.mov

Expensify Logs Dec 10 2024.txt

View all open jobs on GitHub

@m-natarajan m-natarajan added Daily KSv2 Needs Reproduction Reproducible steps needed Bug Something is broken. Auto assigns a BugZero manager. labels Dec 10, 2024
Copy link

melvin-bot bot commented Dec 10, 2024

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

@MelvinBot
Copy link

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

@Christinadobrzyn Christinadobrzyn added the Internal Requires API changes or must be handled by Expensify staff label Dec 10, 2024
@Christinadobrzyn
Copy link
Contributor

Christinadobrzyn commented Dec 10, 2024

I think this needs to be internal and I think it's part of the expense project.

@lakchote let me know if you might have the bandwidth to work on this or I'll reach out to the team.

@Christinadobrzyn Christinadobrzyn added Hot Pick Ready for an engineer to pick up and run with and removed Hot Pick Ready for an engineer to pick up and run with labels Dec 10, 2024
@Christinadobrzyn
Copy link
Contributor

Discussing next steps here - https://expensify.slack.com/archives/C049HHMV9SM/p1733821770177699

Just a heads up that I'm going to be ooo Dec 12 - 13th. Back on Monday 16th. I'm not going to assign this to a BZ teammate but if anything is urgent, please reach out to the team for a volunteer.

@Christinadobrzyn
Copy link
Contributor

I'll check on the Slack convo on Monday when I'm back

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. Daily KSv2 Internal Requires API changes or must be handled by Expensify staff Needs Reproduction Reproducible steps needed
Projects
Status: No status
Development

No branches or pull requests

3 participants