Skip to content
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

Transactions list shows estimated for deposits (payouts) in the past #7375

Closed
haszari opened this issue Oct 5, 2023 · 5 comments
Closed
Labels
category: core WC Payments core related issues, where it’s obvious. component: reporting Issues related to Reporting component: transactions Issues related to Transactions focus: payments acceptance & processing good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.

Comments

@haszari
Copy link
Contributor

haszari commented Oct 5, 2023

Describe the bug

The transactions list has a Deposit date column.

  • ✅ For transactions that will get paid out in the future, it says Estimated Oct 11, 2023
  • 🧐 For transactions that have already been paid out, it says Estimated Oct 1, 2023 aka Estimated [in the past]
Screenshot 2023-10-05 at 2 05 18 PM

To Reproduce

  1. Set up WooPayments and ensure you have purchases and payouts in the past (this might take time to set up, can see on any store that's been live for a few payouts).
  2. Go to Dashboard > Payments > Transactions.
  3. Ensure Deposit date column is visible.
  4. View transactions from before the most recent deposit.

Actual behavior

Estimated 20 June 2021

Expected behavior

Paid 20 June 2021 or similar. Wording might need care when deposit is in transit, or other situations close to payout date.

@haszari haszari added type: bug The issue is a confirmed bug. component: transactions Issues related to Transactions labels Oct 5, 2023
@jessy-p jessy-p added the category: core WC Payments core related issues, where it’s obvious. label Oct 5, 2023
@haszari
Copy link
Contributor Author

haszari commented Oct 5, 2023

This issue could be handled by Helix or a team that looks after transaction list. IMO this is a core issue, it's not really about Disputes.

@zmaglica
Copy link
Contributor

@haszari We have discussed about this issue in Gamma prioritization call, and we decided that the issue is not within the core. This is the perfect example of the issue that affects multiple team responsibilities. Since it affects reports, I am also looping @anu-rock too, so we can decide could Fusion put this issue under its wing.

@anu-rock Do you think that the team Fusion can work on this issue?

For now, I will move this issue to the Other Teams Queue, as a part of the Gamma Triage process.

@anu-rock
Copy link
Contributor

@zmaglica Yes, it does make sense to tackle this issue as part of the reporting maintenance backlog. I'll put it there.

@anu-rock anu-rock added component: reporting Issues related to Reporting priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. labels Feb 15, 2024
@haszari
Copy link
Contributor Author

haszari commented Feb 15, 2024

Thanks @anu-rock ! The behaviour is likely different now that we've stopped estimating future deposits, the bug might not be happening anymore - worth retesting before starting work!

@haszari
Copy link
Contributor Author

haszari commented Mar 11, 2024

Closing – we fixed this when we removed estimated future payouts (and linking of transactions to future payouts). See relevant issue:

@haszari haszari closed this as completed Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: core WC Payments core related issues, where it’s obvious. component: reporting Issues related to Reporting component: transactions Issues related to Transactions focus: payments acceptance & processing good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.
Projects
None yet
Development

No branches or pull requests

4 participants