Ruby group capstone: set up your Kanban board

[imranhossainemi]

Project link : https://github.com/imranhossainemi/catalog_of_my_things/projects/1

In this group project , we are three people. Whom divide the work in this list:

1. Imran Hossain @imranhossainemi
2. Santosh Konappanavar @Santosh-Konappanavar
3. Ikoote Rasuli @ikoote1

[uwadonat]

Hi@Team,

Good job so far! There are some issues that you still need to work on to go to the next project but you are almost there!

## Highlights - All kanban board features were implemented ✔️ ## Required Changes ♻️ - [x] Let's add all project [features](https://github.com/microverseinc/curriculum-ruby/blob/main/group-capstone/catalog_of_my_things_divided.md) and remember also to mention group tasks  Cheers and Happy coding!👏👏👏 Feel free to leave any questions or comments in the PR thread if something is not 100%. Please, remember to tag me @uwadonat in your question so I can receive the notification. ------ **_Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise._** ------ _As described in the [Code reviews limits policy](https://microverse.zendesk.com/hc/en-us/articles/1500004088561) you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using [this form](https://airtable.com/shrQAqnBwek5a0O0s)._

[BregornOriginal]

Hi @Team 💯

Good job so far!

There are some issues that you still need to work on to prepare your project for the final evaluation but you are almost there!

• [x] Kindly as was requested by the previous reviewer, create the corresponding cards for each member of the team. This means you need to spread all the tasks in different sub-tasks and give points and assign members to them as it's required for the project.

Example:

For the group task

Create a new Issue for each task and assign all the member teams for this task. And so on, for each task in the requirement. Same with the task for team members #1, #2 and #3

Remember that the Kanban board it's really useful to track the work of a team member and also to structure a project into small tasks to make the work easier 💯

Suggested changes

Check the comments under the review.

You can use as many of my suggestions as you want. If there is anything you would like to skip - feel free to do that. However, I strongly recommend you to take them into account as they can make your code better._

You can also consider:

• x
• y
• z

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

[ShadyShawkat]

Hi Team,

Great work on making the changes requested by a previous reviewer 👏 You've done well implementing some of the requested changes, but there are still some which aren't addressed yet.

Required Changes ♻️

• [ ] Currently, all tasks have no description. Please make sure that all tasks have corresponding descriptions according to the project's requirements.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

---

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

[KanzaTahreem]

Approved 🥳

Hi @imranhossainemi, @Santosh-Konappanavar & @ikoote1 🙋‍♀️

Great work implementing the suggested changes 💪 Your project is COMPLETE! 🚀 Congratulations!

Highlights 🎯

There are some excellent points that you have made perfectly. Keep up the great work! 👏

• ✅ All cards have description, perfect!
• ✅ Group tasks and individual tasks are defined
• ✅ All cards have points, great job

Optional suggestions ❕

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

N/A

Cheers and Happy coding!👏👨‍💻💻

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

---

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.