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

[Bug]: NYNAB import - importing transaction with a transfer as a split payment causes transfer to get treated as uncategorised payment #1835

Closed
1 task done
Marethyu1 opened this issue Oct 28, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@Marethyu1
Copy link
Contributor

Marethyu1 commented Oct 28, 2023

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Consider the following transaction:
image

It is payment to the store, but it also contains a transaction split which is a transfer of $50 to the savings account.
If you try to import a transaction like this, the sub transaction gets treated as an uncategorised payment instead:
Screenshot 2023-10-29 at 12 42 25 PM

I have attached a modified demo budget which you can use to reproduce the behaviour.
ynab5-demo-budget.json
ynab5-demo-budget-working.json

Expected behaviour: imported transaction contains a sub transaction which is a transfer to the savings account
Actual behaviour: imported transaction contains a sub transaction which is an uncategorised payment.

👋 also hello this is my first issue - let me know if I need to add anything else - thanks

What error did you receive?

It doesn't result in an error it just doesn't work as expected.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Safari

Operating System

Mac OSX

@youngcw
Copy link
Member

youngcw commented Nov 7, 2023

@Marethyu1 Is this fully fixed now that your PR was merged?

@Marethyu1
Copy link
Contributor Author

Hey @youngcw it works for me in master. Im not sure what the process is for closing these issues off. Not sure if it is best to wait until the issue has been included in a full release or if I should be fine to close it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants