github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #1224] [MERGED] Fix importing transfers from YNAB4/5 #3606

New Issue
Closed
opened 2026-02-28 20:44:08 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:44:08 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/1224
Author: @j-f1
Created: 6/28/2023
Status: ✅ Merged
Merged: 7/1/2023
Merged by: @j-f1

Base: master ← Head: jed/ynab-transfer-import

📝 Commits (3)

  • daca2ce Set the ID correctly for imported split transactions in YNAB4
  • 8686d82 Also fix YNAB5
  • b1da30b Add release note

📊 Changes

3 files changed (+11 additions, -0 deletions)

View changed files

📝 packages/import-ynab4/importer.js (+1 -0)
📝 packages/import-ynab5/importer.js (+4 -0)
➕ upcoming-release-notes/1224.md (+6 -0)

📄 Description

Fixes #1220. Previously, the importer wasn’t correctly setting the ID of subtransactions on split transactions. This was mostly fine since the ID wasn’t used for much, but as shown in the referenced issue, if a subtransaction is a transfer, it won’t be correctly matched with its pair in the other account. Future imports will now handle this correctly. I’m not sure if there is a way we could detect and fix this in existing budgets.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/1224 **Author:** [@j-f1](https://github.com/j-f1) **Created:** 6/28/2023 **Status:** ✅ Merged **Merged:** 7/1/2023 **Merged by:** [@j-f1](https://github.com/j-f1) **Base:** `master` ← **Head:** `jed/ynab-transfer-import` --- ### 📝 Commits (3) - [`daca2ce`](https://github.com/actualbudget/actual/commit/daca2cea5c1cf27eed00028479ef569901034a77) Set the ID correctly for imported split transactions in YNAB4 - [`8686d82`](https://github.com/actualbudget/actual/commit/8686d82c6ff01835c9d84d547961802e8fd24a64) Also fix YNAB5 - [`b1da30b`](https://github.com/actualbudget/actual/commit/b1da30b163bdbebfd7657b65b76556b59624f79f) Add release note ### 📊 Changes **3 files changed** (+11 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/import-ynab4/importer.js` (+1 -0) 📝 `packages/import-ynab5/importer.js` (+4 -0) ➕ `upcoming-release-notes/1224.md` (+6 -0) </details> ### 📄 Description Fixes #1220. Previously, the importer wasn’t correctly setting the ID of subtransactions on split transactions. This was mostly fine since the ID wasn’t used for much, but as shown in the referenced issue, if a subtransaction is a transfer, it won’t be correctly matched with its pair in the other account. Future imports will now handle this correctly. I’m not sure if there is a way we could detect and fix this in existing budgets. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 20:44:08 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#3606
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?