Open m-natarajan opened 4 days ago
Triggered auto assignment to @dylanexpensify (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.
Edited by proposal-police: This proposal was edited at 2024-09-26 15:28:39 UTC.
The approver is unable to resolve the duplicate, as no resolve duplicate button appears
New feature
function getDuplicatedReportID(reportID: string){
return Object.values(allReportActions?.[`reportActions_${reportID}`] ?? {}).find(action=>{
const transactionID = ReportActionsUtils.isMoneyRequestAction(action) && ReportActionsUtils.getOriginalMessage(action)?.IOUTransactionID
if(!transactionID){
return false;
}
return TransactionUtils.isDuplicate(transactionID)
})?.childReportID
}
MoneyReportHeader
get the duplicated report ID const duplicatedReportID = useMemo(()=>{
return ReportUtils.getDuplicatedReportID(moneyRequestReport?.reportID ?? '')
},[moneyRequestReport?.reportID])
And then show the Resolve duplicate
button if duplicatedReportID
is not undefined
{duplicatedReportID && !shouldUseNarrowLayout && (
<Button
success
text='Resolve duplicates'
style={[styles.p0, styles.ml2]}
onPress={() => {
Navigation.navigate(ROUTES.TRANSACTION_DUPLICATE_REVIEW_PAGE.getRoute(duplicatedReportID, Navigation.getReportRHPActiveRoute()));
}}
/>
)}
https://github.com/user-attachments/assets/006ee995-0cb3-4f57-8bd5-73bbf7b2c81a
One way we could handle this is by adding a Resolve duplicates
button to the header, like so:
cc @JmillsExpensify @Expensify/design
Job added to Upwork: https://www.upwork.com/jobs/~021839321413603387914
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External
)
Nice, I like that idea!
Updated proposal to fit with the new design
Same. Looks good to me
Am I missing something or one expense should auto resolve duplicates? What are we marking duplicate against?
@shubham1206agra The duplicates might be in a different report
Thanks for the proposal @daledah
We should remove canUseDupeDetection check in
I am not sure how is the change related to this issue. Dupe Detection is behind beta and the function is serving the purpose.
Can you please add more details to the 2nd point in your proposal.
@sobitneupane Thanks for your feedback, I updated the proposal to add more details and video result
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.40-1 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: @JmillsExpensify Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1727339112704349
Action Performed:
Expected Result:
The approver is able to resolve a duplicate
Actual Result:
The approver is unable to resolve the duplicate, as no resolve duplicate button appears
Workaround:
Unknown
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
Issue Owner
Current Issue Owner: @sobitneupane