mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-11 04:32:39 -05:00
[Feature] Allow parsing transaction content #1662
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1662
Reference in New Issue
Block a user
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?
Originally created by @Chuckame on GitHub (Dec 11, 2024).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
The bank data coming from Gocardless isn't that perfect. I would like to fix the dates, the payee and the notes depending on the transaction itself.
An example : I have a deferred credit card, which puts the transaction dates only when it's really debited. On my side, to manage and schedule transactions, it's a pain as all the transactions of the month appear in one day.
But, the real date is present inside the transaction description for a bank, or in the transaction ID in another bank.
I already checked with Gocardless for the date issue, but they answer that the bank itself provides them wrongly (standards are so long in open banking to be widely applied...). However, this feature is not only for the date issue, but also allowing cleaning or rewording transactions.
Describe your ideal solution to this problem
I would be awesome to provide a way to set a transaction field (date, payee, notes) in a rule based on the output of the catches groups from the regex applied on the original field (id, description).
Maybe for the first experimental try, just a regex group should be enough. Then, we could have a more complete ui for non-tech people to build the regex based on some standard usage (spaces, numbers, letters,...).
Teaching and learning
Just in the rules ui which isn't that big, so maybe a checkbox to enable regex or advanced content extraction.
@github-actions[bot] commented on GitHub (Dec 11, 2024):
✨ Thanks for sharing your idea! ✨
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).
The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+
Don’t forget to upvote the top comment with 👍!
@UnderKoen commented on GitHub (Dec 11, 2024):
Does https://github.com/actualbudget/actual/issues/3606 satisfy?
@Chuckame commented on GitHub (Dec 11, 2024):
@UnderKoen yes, exactly that. I'll propose to extract from the condition to avoid regex duplicates.
I've searched but probably with the wrong words 😱 Sorry for the noise, thanks!