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

Add the ability to search / filter expenses #430

Open
Norde opened this issue Mar 18, 2019 · 5 comments
Open

Add the ability to search / filter expenses #430

Norde opened this issue Mar 18, 2019 · 5 comments

Comments

@Norde
Copy link

Norde commented Mar 18, 2019

In order to easily find a particular transaction (or a type of transaction).

The filter could take into account independently or cumulatively :
Amount / Date / Payor / Recipient / Category ... (with range where it's relevant)

@almet
Copy link
Member

almet commented Mar 20, 2019

Thanks for taking the time to open this discussion.

Why not :-) I personally don't have the use case (a text search usually does the trick for me, using the browser.

I'm curious if anyone else thinks this is needed?

@Norde
Copy link
Author

Norde commented Mar 20, 2019

The search will gain a lot of flexibility and performance with such a tool (Just a filter showing only operations that contain a specific term would be great!)

Who has never complained when looking for a transaction during accounts check?

But my case may be special because I am part of a very old roommate, so the expense history is very long ^^

@jerryshueh
Copy link

I came across this cool little app while looking for a way to split cottage expenses among friends. I think this feature is within my power to attempt. Please let me try my hand at this!

@almet
Copy link
Member

almet commented Nov 15, 2019 via email

@nachow16
Copy link

nachow16 commented Apr 3, 2020

hey @almet ,
@allisongu and I would like to work on this feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants