-
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
[Hold for payment 2024-03-06] [$500] Tag - Selected tag is missing in Split report when split scan is created offline #36237
Comments
Job added to Upwork: https://www.upwork.com/jobs/~0174fb7f86a4edd9a2 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @johncschuster ( |
We think that this bug might be related to #vip-split-p2p-chat-groups |
ProposalPlease re-state the problem that we are trying to solve in this issue.When completing the scan split manually, the tag & category are not updated optimistically in the individual transactions. What is the root cause of that problem?When completing the Split Bill, we do not pass the updated category & tag for each individual IOU transaction: Lines 2231 to 2242 in ad3d78c
What changes do you think we should make in order to solve the problem?When completing the Split Bill, we need to pass the category & tag for each individual IOU transaction as well: const oneOnOneTransaction = TransactionUtils.buildOptimisticTransaction(
isPolicyExpenseChat ? -splitAmount : splitAmount,
currency ?? '',
oneOnOneIOUReport?.reportID ?? '',
updatedTransaction.comment.comment,
updatedTransaction.modifiedCreated,
CONST.IOU.TYPE.SPLIT,
transactionID,
updatedTransaction.modifiedMerchant,
{...updatedTransaction.receipt, state: CONST.IOU.RECEIPT_STATE.OPEN},
updatedTransaction.filename,
+ undefined,
+ updatedTransaction.category,
+ updatedTransaction.tag,
); Result:Screen.Recording.2024-02-09.at.15.57.37-compressed.mp4What alternative solutions did you explore? (Optional) |
@johncschuster, @rushatgabhane Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@johncschuster, @rushatgabhane Eep! 4 days overdue now. Issues have feelings too... |
bumped in Slack cc @arielgreen as this might be related to #vip-split |
@paultsimura's proposal looks good to me 🎀 👀 🎀 |
Triggered auto assignment to @danieldoglas, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
On a sidenote, we should consider passing an object We have very few occurrences. We can fix it in same PR. @paultsimura @danieldoglas what do you think? |
hm, I think that will make that method different from all the other @rushatgabhane can you propose that on #expensify-open-source so we can have more opinions on it? |
@danieldoglas if you agree with the proposal review, could you please assign me here so I could start with the recordings? The parameters format can be discussed within the PR IMO. |
📣 @paultsimura 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Thanks. The PR is ready for review: #36759 |
@johncschuster could you please attach payment summary, thanks 🙇 |
payment request here https://staging.new.expensify.com/r/1368693063642793 |
Sorry for the delay! I'm on the payment summary in just a few minutes |
Payment Summary:Contributor: @paultsimura - $500 paid via Upwork |
I believe it's due payment on March 7, right? |
Payment has been issued to @paultsimura 🎉 |
$500 approved for @rushatgabhane based on summary. |
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.39.0
Reproducible in staging?: y
Reproducible in production?: y
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: Applause - Internal Team
Slack conversation:
Issue found when executing PR #35913
Action Performed:
Precondition:
Expected Result:
The selected tag appears on Tag row.
Actual Result:
The Tag row is missing the selected tag.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6373664_1707488765500.20240209_034402.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: