github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[PR #736] [MERGED] Store payee in imported_payee during ynab4/ynab5 import #52595

New Issue
Closed
opened 2026-04-30 20:59:39 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 20:59:39 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/736
Author: @ostat
Created: 3/10/2023
Status: ✅ Merged
Merged: 4/6/2023
Merged by: @MatissJanis

Base: master ← Head: ynab_inport

📝 Commits (4)

  • 7bd6024 Store payee in imported_payee during ynab4/ynab5 import
  • 383c6f9 Merge branch 'actualbudget:master' into ynab_inport
  • e19dc46 remove null coalesce as its not needed and is breaking CI.
  • 5c7e43b Add release note

📊 Changes

3 files changed (+15 additions, -2 deletions)

View changed files

📝 packages/import-ynab4/importer.js (+6 -2)
📝 packages/import-ynab5/importer.js (+3 -0)
➕ upcoming-release-notes/736.md (+6 -0)

📄 Description

Updated the ynab4 and ynab5 importer to store the payee in the imported_payee field.

This is helpful for future targeting rules against the imported_payee field post import.
I was able to test the ynab4 import, however I don't have a ynab5 file to test with.

Instructions to reproduce.

This ynab4 file only has two transactions, both contain the word company.
testynab4~C3738CB5.ynab4.zip

  • Import the file using the usual process.
  • You can confirm there are two transactions.
  • Go to the rules section.
  • Create a new rule, add filter for imported payee contains company
  • You will see the imported payee fields are populated

image

🔄 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/736 **Author:** [@ostat](https://github.com/ostat) **Created:** 3/10/2023 **Status:** ✅ Merged **Merged:** 4/6/2023 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `ynab_inport` --- ### 📝 Commits (4) - [`7bd6024`](https://github.com/actualbudget/actual/commit/7bd60240e5a8b10cabb87f2d3a72df383756b1d8) Store payee in imported_payee during ynab4/ynab5 import - [`383c6f9`](https://github.com/actualbudget/actual/commit/383c6f9b10c31149aa12588a574bb3bea5613055) Merge branch 'actualbudget:master' into ynab_inport - [`e19dc46`](https://github.com/actualbudget/actual/commit/e19dc4684401f310433f08f75ee3a83f0ddf9ff5) remove null coalesce as its not needed and is breaking CI. - [`5c7e43b`](https://github.com/actualbudget/actual/commit/5c7e43bdc4b3fed6a19b5876af597905a142ca61) Add release note ### 📊 Changes **3 files changed** (+15 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `packages/import-ynab4/importer.js` (+6 -2) 📝 `packages/import-ynab5/importer.js` (+3 -0) ➕ `upcoming-release-notes/736.md` (+6 -0) </details> ### 📄 Description Updated the ynab4 and ynab5 importer to store the **payee** in the **imported_payee** field. This is helpful for future targeting rules against the imported_payee field post import. I was able to test the ynab4 import, however I don't have a ynab5 file to test with. **Instructions to reproduce.** This ynab4 file only has two transactions, both contain the word **company**. [testynab4~C3738CB5.ynab4.zip](https://github.com/actualbudget/actual/files/11153757/testynab4.C3738CB5.ynab4.zip) - Import the file using the usual process. - You can confirm there are two transactions. - Go to the rules section. - Create a new rule, add filter for `imported payee contains company` - You will see the `imported payee` fields are populated ![image](https://user-images.githubusercontent.com/2128234/229937572-239b98a4-d385-4ec7-a24d-33e3bdea6208.png) --- <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-04-30 20:59:39 -05: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#52595
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?