Save for later

[alexanmtz]

A new option on task page action bar, with "Save for later" label with a save icon. And once it is clicked and saved, it should switch to "Remove from Save for later" with the delete icon. Then when we are on task explorer, it should have a new tab item with the label "Saved for later", with the issues filtered by the saved ones.

We should create a model with a user with many saved issues.

Why

We should be able to collect issues we're interested in and check later.

Level

Beginner

How to reproduce the user scenario

• Create a user
• Import an issue
• We should have a button "Save for later"

Tips

Check our existing models

[topseySuave]

Hello @alexanmtz I would like to work on this issue and would appreciate I am assigned to it.

[alexanmtz]

Hello @topseySuave, you're now assigned to work on this issue 👍

[alexanmtz]

Hello @topseySuave , I think you're missing the step in our README to copy .env.example to .env to have the env variables set.

[topseySuave]

I got it already sorry, thanks.

[topseySuave]

Hi, Good day @alexanmtz I have currently added the action button on the frontend and working on actually saving a task in the database, but I have this issue where I created a migration file as well as the model after running sequelize migration:create --name saveTask and run npm run migrate I get only this migration

> node migrate.js up

(node:42393) DeprecationWarning: Using the automatically created return value from client.query as an event emitter is deprecated and will be removed in pg@7.0. Please see the upgrade guide at https://node-postgres.com/guides/upgrading
20200323014820-create-plan migrating
========
========

the new migration file 20200403235735-saveTask I have gets ignored, please do you know how I can go about this?

Thanks.

[alexanmtz]

Hello @topseySuave, can you try to run npm run migrate instead?

[Adekoreday]

This issue has been fixed in PR #640 once merged
Kindly use the migration update command
@topseySuave