-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Fix Create Report row showing wrong workspace name when moving expenses #85927
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
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6c808de
Fix: Display correct workspace name in Create Report row when moving …
MelvinBot 3f45050
Fix: use default workspace for report creation in move-to-report flow
MelvinBot 75f5b8f
Merge remote-tracking branch 'origin/main' into claude-fixCreateRepor…
MelvinBot eb04d96
Merge remote-tracking branch 'origin/main' into claude-fixCreateRepor…
MelvinBot 5b6796c
Merge remote-tracking branch 'origin/main' into claude-fixCreateRepor…
MelvinBot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using only
transactionPolicyIDhere regresses theIOURequestEditReportper-diem flow, because that caller now passesundefinedwhilecreateReportForPolicystill creates the new report inselectedReportPolicy. In that case,IOURequestEditReportCommonvalidates per-diem moves against the active/default workspace instead of the actual destination policy, so users with multiple workspaces can see the wrong workspace label and may be blocked by the per-diem warning modal even though creating in the source workspace would be valid.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MelvinBot please check this comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I investigated this comment and it's valid — there is a real mismatch in the per-diem flow introduced by this PR.
The problem
For per-diem transactions in IOURequestEditReport:
Concrete scenario
User has per-diem expenses on workspace B (non-default), default workspace is A:
Why it regressed
Before this PR, IOURequestEditReportCommon used selectedReport?.policyID ?? transactionPolicyID, which resolved to the source workspace — keeping display, validation, and creation aligned. The PR removed this fallback, breaking consistency for the per-diem path.
Suggested fix
Either: