-
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
Track expense - Track distance expense does not show up in self DM #40029
Comments
Triggered auto assignment to @NikkiWines ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
We think that this bug might be related to #wave-collect - Release 1 |
cc: @neil-marcellini since it looks like this is a result of #39190 |
Looks like adding a second track expenses results in both track expenses showing in the self-DM. Regardless this looks like it's currently behind a beta, so going to remove the blocker label. |
This might be a problem before distance track expense. @paultsimura Can you confirm this problem's origin? |
I cannot verify 100% because the tracking expense removal fails on BE currently. |
I'll take this over since it might be related to my PR. It sounds like that PR above fixed this. I'll test on staging now. |
Yep, fixed. Thanks @paultsimura! Screen.Recording.2024-04-11.at.10.46.11.AM.mov |
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: 1.4.62-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #39190
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Expected Result:
The track distance expense will show up in self DM.
Actual Result:
The track distance expense does not show up in self DM, but it shows preview in LHN.
This issue only happens when there is no track expense in the self DM. The missing distance request reappears after creating the second request.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6444887_1712774076814.20240411_022950.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: