-
Notifications
You must be signed in to change notification settings - Fork 21
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
Improve recurrent transactions visibility in the transaction-list page #254
Comments
I'm excited to work on it, not sure when I will start to, perhaps tomorrow. Shall I comment when I start just to be sure two devs don't work on the same? |
Yes please, and assign yourself the task if you want too :) Thanks a lot!! |
Last time I've checked I did not have permission to assign myself, must be repository permission settings 🤔 |
Done 😊 |
Hi @vincius0000, please contact me at [email protected] if you have any questions or if you want to share your progress |
Fully agree with this. Additionally, I'm thinking perhaps we could offer the option of notifying the user when the deadline of a pending transaction has passed? Otherwise it's easy to forget marking them as paid. What do you think? |
Yes, I totally agree. However, we don't have right now any kind of notifications implemented in the app, so it will require a bit of work to introduce them. That would be part of another task, but for sure a nice addition to the app. |
Prerequisites
Current Behavior
With the current app version, we can only see the next item that will come from a recurring transaction, without any extra information. Also, there is no easy way to distinguish future transactions or pending transactions from the rest.
Expected Behavior
It is proposed to do something similar to what the excellent 1Money app is doing right now:
Here we have the should consider the following points:
Steps to Reproduce
To generate a good test for this functionality, it would be good to create at least two recurring transactions, with a small periodicity (weekly or daily) or without an end date. With this, we could obtain a few future transactions and try to filter by dates and other parameters
Additional Information
This issue is based on the discussion generated in #243, with @shinebrillant, @vincius0000 and @enrique-lozano as participants. We should also consider the more in-deep analysis made here.
As always, if you want to collaborate on this, PRs are accepted.
The text was updated successfully, but these errors were encountered: