ck3g / homebugh Goto Github PK

test

It can be a great idea to have a demo account, so everyone can test drive the application without the need to register.
The demo account should have prepopulated data, and should "reset" the data once a day.
The demo account should not have the ability to change the password.

Sub-issues:

• Add demo_user column to users
• Register a demo account
• Create a script to populate the demo account with dummy data
• Create a script to reset the data for the demo account
• Schedule reset script to run once a day
• Prevent demo users from changing the password and the email
• Remove ability to update demo profiles
• Add information about demo account to home page
• Add information about demo account to login page

Create RecurringPaymentsController#destroy action and allow to delete existing recurring payments.

Contributes to #31

Depends on #61

Accounts summary should display accounts only with show_in_summary == true.

Contributes to #32

Depends on #57

Contributes to #33

Dependencies

• Add demo_user column to users

Login page should display demo account login credentials.

Create RecurringPaymentsController#edit and #update actions and allow to update existing recurring payments.

Contributes to #31

Depends on #61

Apparently, confirmation mail lacks encryption thus deemed by gmail as spam.

Read more: https://medium.com/cedarcode/rails-5-2-credentials-9b3324851336

Render a Cookie Consent notice to a user at the top of the page.

Check the presence of the cookie_consent_accepted cookie on every page load.

If the cookie does not exist, render the "Cookie Consent" popup at the top of the page.
The "Cookie Consent" popup should contain:

• "Cookie Consent" title
• "We use cookies to give you the best online experience. By using our website, you agree to our use of cookies." message
• "OK" button.

Clicking on the button creates a cookie_consent_accepted cookie with the true value.

Contributes to #33

Override Devise::RegistrationsController#update and skip profile update when the current user is a demo_user

Dependencies

• #34

Contributes to #33

Demo account should not have the ability to change the password and the email

Replace Edit Profile form /users/edit with the static text:

Email: <demo user Email>
Password: demo1234

The /users/edit page should behave differently for demo users.

When the logged-in user (or current_user) is a demo_user? the edit profile should not let to update the email and password for that user. It can be done by making the form read-only, or by replacing the form with the text information.

When the logged-in user is a regular user (demo_user? == false), the form should work as it works now. The user should be able to update the email and password.

Dependencies

• Add demo_user column to users - Once implemented, will provide User#demo_user? method.

• Drop coffee-rails gem
• Convert transactions.js.coffee to vanila JS

Contributes to #33

Dependencies

• Add demo_user column to users
• Create a script to reset the data for the demo account

Use whenever gem run a daily cron job to reset demo user data.

Create a User Profile page.

• The page should render the current user's email.
• The page should require authorization
• The page should have an /users/profile URL.

Migrate to the newest possible version of factory_bot_rails.

Checkout Upgrade from factory_girl guide.

Create a boolean show_in_summary column in the accounts table, with the default value of true

Contributes to #32

Allow to set show_in_summary value from create account page (/accounts/new).

Contributes to #32

Depends on #57

At the moment the balance of all accounts (on top of the page) displays funds from all the accounts.

There should be an option to hide some accounts from the balance overview.

• Create a boolean show_in_summary column in the accounts table, with the default value of true
• Allow to set show_in_summary value from create account page (/accounts/new).
• Allow to update show_in_summary value on edit account page (/accounts/:id/edit).
• Accounts summary should display accounts only with show_in_summary == true.

There are certain transactions (payments) that are repeating from time to time. Some examples of those transactions are monthly internet bill, a Netflix subscription, etc.

Sometimes it's easy to forget some of these recurring payments, especially when there are a bunch of them at the moment.

The goal here is to remove the burden of keeping all these repetitive transactions in mind. The application has to provide a way to create a list of such transactions. That list can play the role of reminders. Also, based on that list the application can suggest filling in a recurring transaction when time is due.

Sub-tasks

• Create a RecurringPayment model
• Add a page to display the list of recurring payments
• Add functionality to create recurring payments
• Add functionality to edit recurring payments
• Add functionality to delete recurring payments
• Add next_payment_on field
• Display the list of due recurring payments above the transactions
• Add the ability to skip a due recurring payment (move to the next period)
• Add the ability to apply a due recurring payment (create a transaction and move to the next period)
• Provide translations for recurring payments

Allow to update show_in_summary value on edit account page (/accounts/:id/edit).

Contributes to #32

Depends on #57

Contributes to #33

Dependencies

• Add demo_user column to users

Create a rake task to update demo account. The task is going to run every day to "reset" the data. The data should match the required data described here.

Prefer updating existing records to drop and re-create.

Contributes to #33

Dependencies

• Add demo_user column to users

Home page should display demo account login credentials.

Fix "Remember me" checkbox position on Sign in page

There is an invalid link to Travis CI in the README file. The correct link is https://travis-ci.org/github/ck3g/homebugh

Contributes to #31

All static text related to recurring payments should be localized.

Create a model with the following fields:

• title: string, not null
• user_id: int, not null
• category_id: int, not null
• account_id: int, not null
• amount: decimal, precision: 10, scale: 2, not null
• frequency_days: int, not null
• frequency: (int, not null, default 0) enum: "daily", "weekly", "monthly", "yearly"

It's not needed with bcrypt

Recurring payments should have next_payment_on DateTime column, to check the next payment date.

Contributes to #31

Create RecurringPaymentsController#new and #create actions and allow to create recurring payments.

Contributes to #31

Depends on #61

Contributes to #33

Add a boolean column demo_user to the users table with the default value of false.

To optimize the user experience it can be converted to create recurring payments from existing transactions.

Clicking a button next to transaction should redirect a user to '/recurring_payments/new' and populate all fields.

Every Pull Request should run trigger Travis CI build and display the result.

Contributes to #33

Dependencies

• Add demo_user column to users

Create a rake task to seed a demo account with dummy data.

Required data

A demo user should have the following data.

• Income category. For example "Salary"
• Several spending categories. For example: "Grocery", "Clothes", "Rent"
• Two accounts: "Cash", "Bank"
• Two budget records
  • "Grocery" - 200
  • "Clothes" - 100
• Several transactions
  • Account: "Bank", Category: "Salary", Amount: 2000, Date: 1st day 2 months ago
  • Account: "Bank", Category: "Rent", Amount: 500, Date: 15th day 2 months ago
  • Account: "Cash", Category: "Grocery", Amount: random 150-250, Date: 3rd day 2 months ago
  • Account: "Bank", Category: "Salary", Amount: 2000, Date: 1st day of the previous month
  • Account: "Bank", Category: "Rent", Amount: 500, Date: 15th day of the previous month
  • Account: "Cash", Category: "Grocery", Amount: random 150-250, Date: 3rd day of the previous month
  • Account: "Cash", Category: "Clothes", Amount: random 100-200, Date: 5th day of the previous month
  • Account: "Bank", Category: "Salary", Amount: 2000, Date: 1st day of the current month
  • Account: "Cash", Category: "Grocery", Amount: random 150-250, Date: today
• Several cash flows:
  • From Account: "Bank", To Account: "Cash", Total Amount: random 500-1000, Date: 2nd day 2 months ago
  • From Account: "Bank", To Account: "Cash", Total Amount: random 500-1000, Date: 2nd day of the previous month
  • From Account: "Bank", To Account: "Cash", Total Amount: random 500-1000, Date: today
• Run ArchiveTransactionsService#archive for last day:
  • 2 months ago
  • of the previous month

TBD

Contributes to #31

A user should be able to move an existing recurring payment to the next period by clicking a button.

The next period calculated from 'next_payment_on + frequency_amount * frequency'

Users (except demo) should be able to remove their accounts with all the data.

Create a "Delete User" page (GET /user/delete).
The page should be accessible only for signed-in users.

The page should contain:

• "Delete this user" title
• "Once you delete a user, there is no going back. Please be certain." warning message
• "Current password" field.
• "Delete this user" button

If the form is submitted with a valid password, the current user should be deleted from the database.
If the password is invalid the user should see the validation error message.

Create RecurringPaymentsController#index action and display the list of existing recurring payments.

Contributes to #31

Depends on #61

Update chartkick to the newest version.

Heads up: there are breaking changes between 2.0 and 3.0

The forgot password form is too narrow.

Page URL /users/password/new

Page URL: https://homebugh.info/users/edit

Add instructions describing how to configure the project on localhost for development. How to seed the DB etc.

The profile page should have a link to Edit profile page.

⚠️ Blocked by #26

• Profile page URL /users/profile (TBD in #26)
• Edit profile page URL /users/edit

Some people may want to use the application on their own hosting provider. It would be great to provide instructions on how to do that.

Add the step-by-step instructions on how to deploy and run the application on Heroku https://www.heroku.com

Suggest users to check spam filter:

Remember: Check your spam filter

If you do not receive the confirmation message within a few minutes, please check your spam or junk e-mail folder and mark the e-mail "not spam", which should allow future messages to get through.