-
Notifications
You must be signed in to change notification settings - Fork 3k
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
CRITICAL: [Actionable Whispers] Changes when categorizing / sharing a tracked expense are not saved #40304
Comments
Job added to Upwork: https://www.upwork.com/jobs/~015eae82d8e6ef3565 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @rayane-djouah ( |
Triggered auto assignment to @garrettmknight ( |
This is something that will need to be fixed in the BE |
Changes are merged- pending deploy |
Just tested and this looks like the tracked expense info is being saved. |
Noice! |
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: N/A
Reproducible in staging?: N/A
Reproducible in production?: N/A
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:
Slack conversation:
Action Performed:
Note: This occurs as part of a feature from this PR
Break down in numbered steps
Expected Result:
The new shared/categorized transaction details should be saved
Actual Result:
They are not
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: