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

Can we make SEPA fields searchable to use them as rule triggers/conditions #8537

Open
3 tasks done
arminreh opened this issue Feb 11, 2024 · 2 comments
Open
3 tasks done
Labels
enhancement Requests for enhancements of existing stuff.

Comments

@arminreh
Copy link

Support guidelines

Description

Hey,

thanks for providing a great personal finance tool.

I have interesting information stored in some of the SEPA fields and am trying to use them in a new rule.
My goal.

  • If source account is "(no name") and sepa_info of some kind = "Foobar"
  • Set source account to "Foobar related account"

Solution

I am failing to make this work, because there are no search values beyond sepa_ct.
I wonder if it would be possible to extend this to also make the other sepa info fields usable in the same way?
Would you be open to me adding this in a PR and are there any pitfalls I should be aware of?

What are alternatives?

If the feature is not there I would consider:

  • storing the sepa information in the notes field instead, so it is available for these kinds of queries

Additional context

The "first" SEPA field search functionality has been added here: #6677
A potential starting place?

@JC5
Copy link
Member

JC5 commented Feb 12, 2024

Good idea, it's on the list! No need to open a PR :)

@JC5 JC5 added the enhancement Requests for enhancements of existing stuff. label Feb 12, 2024
Copy link
Contributor

Hi there!

This is an automatic reply. Share and enjoy

This issue has been marked as an enhancement. The requested enhancement to an existing feature will become a part of Firefly III or the data importer in due course.

If you come across this issue, please be aware there is NO need to reply with "+1" or "me too" or "I need this too" or whatever. Such comments are not helpful, and do not influence the roadmap. Your comment may be 💀 deleted. You can subscribe to this issue to get updates.

Thank you for your contributions.

@JC5 JC5 added this to the firefly-iii-v6.2.0 milestone Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Requests for enhancements of existing stuff.
Projects
Status: To do
Development

No branches or pull requests

2 participants