ay1920s1-cs2103t-t12-1 / pluswork Goto Github PK

View Code? Open in Web Editor NEW

This project forked from nus-cs2103-ay1920s1/addressbook-level3

0.0 5.0 5.0 54.46 MB

Address Book - Level 3

Home Page: https://nus-cs2103-ay1920s1.github.io/addressbook-level3/

License: Other

Shell 0.25% Java 96.48% CSS 3.28%

pluswork's Introduction

+Work

"Smash those deadlines"

+Work is a desktop project management application. It has a GUI but most of the user interactions happen using a CLI (Command Line Interface).
The application is targeted at NUS students who are project leaders for organisations, school work or CCA.

Site Map

Acknowledgements

Some parts of this sample application were inspired by the AddressBook-Level3 project created by SE-EDU Initiative.
Libraries used: JavaFX, Jackson, JUnit5, itext, iCal4j

Licence : MIT

pluswork's People

Contributors

Watchers

Forkers

seahlynn ambhinav gabrielseow arunbecoding elsakoh

pluswork's Issues

Unable to fire member off their given assignments

The given member was assigned a task, but was unable to be removed the character.

_{[original: Kyzure/ped#7]}

As a project leader, I change task status

Integrate basic Ui framework

Allow user to switch between the following views:

Dashboard (without a member list)
List of tasks
List of members

Wrong information in Summary portion of User guide

There are several outdated commands that are still in the Summary portion of the user guides that are not changed.

_{[original: Kyzure/ped#11]}

As a project leader with a long-term project with ad-hoc members, I can change members working on a task

Wrong information in User Guide for adding task

User Guide claimed to use add-task [t/TASK_NAME], when to add a task, we have to use add-task[tn/TASK_NAME]. The application itself will tell you to use tn/TASK_NAME and throw an error when using t/TASK_NAME.

_{[original: Kyzure/ped#2]}

Remove address package

Feedback on week 10 project progress for CS2103T-T12-1

Team progress for mid-`v1.3`

Mid-milestone progress reports are FYI only. They are not graded.

Milestone v1.3 managed systematically
- A suitable deadline set [2019-10-30] (:heavy_check_mark: well done!)
- Issues/PRs allocated to it #75 #68 #64 (:heavy_check_mark: well done!)
A new jar file has been released on GitHub. (:heavy_check_mark: well done!)

Individual progress of @ambhinav for mid-`v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #64 #38 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past week e.g., #76 #67 #63 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past week e.g., #76 #73 #72 (:heavy_check_mark: well done!)
Merged PRs that update puml/png files files during the past week e.g., #72 #67 (:heavy_check_mark: well done!)

Individual progress of @ArunBeCoding for mid-`v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #39 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past week e.g., #71 #62 #61 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past week e.g., #71 (:heavy_check_mark: well done!)
Merged PRs that update puml/png files files during the past week e.g., (:exclamation: try to do by next milestone)

Individual progress of @elsakoh for mid-`v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #75 #43 #35 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past week e.g., #53 #74 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past week e.g., #74 (:heavy_check_mark: well done!)
Merged PRs that update puml/png files files during the past week e.g., (:exclamation: try to do by next milestone)

Individual progress of @gabrielseow for mid-`v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #43 #42 #36 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past week e.g., #52 #47 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past week e.g., #69 (:heavy_check_mark: well done!)
Merged PRs that update puml/png files files during the past week e.g., #69 (:heavy_check_mark: well done!)

Individual progress of @seahlynn for mid-`v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #68 #58 #57 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past week e.g., #70 #50 #49 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past week e.g., #70 (:heavy_check_mark: well done!)
Merged PRs that update puml/png files files during the past week e.g., #70 (:heavy_check_mark: well done!)

Tutor: @junrong09

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-24 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

As a new user, i want to see usage instructions

Autocomplete feature for all existing commands

add support for autocomplete so that users dont have to keep checking the user guide for command syntax or rely on error messages

Application starts not in full screen, and the application has certain portions cut off instead of resizing

_{[original: Kyzure/ped#6]}

Feedback on week 7 team project progress for CS2103T-T12-1

Team progress for v1.1

Product website available at the expected URL(:heavy_check_mark: well done!)
PR created from team repo to our repo(:heavy_check_mark: well done!)
README page:
- Some parts not related to your product are removed(:heavy_check_mark: well done!)
- se-education.org acknowledged(:heavy_check_mark: well done!)
- Ui.png has been updated(:heavy_check_mark: well done!)
Product website title changed to match your product(:heavy_check_mark: well done!)
User Guide: some content has been updated(:heavy_check_mark: well done!)
Developer Guide: some content has been updated(:exclamation: try to do by next milestone)
Team repo git tagged as v1.1(:exclamation: try to do by next milestone)

Individual progress of @ambhinav for v1.1

Team repo forked to your GitHub account https://github.com/ambhinav/main (:heavy_check_mark: well done!)
Used forking workflow:
- Created PRs #4 (:heavy_check_mark: well done!)
- Gave review comments to other PRs (:exclamation: try to do by next milestone)
Merged updates to documents(:exclamation: try to do by next milestone)
ambhinav.png uploaded and linked from AboutUs page, merged(:exclamation: try to do by next milestone)

Individual progress of @ArunBeCoding for v1.1

Team repo forked to your GitHub account https://github.com/arunbecoding/main (:heavy_check_mark: well done!)
Used forking workflow:
- Created PRs (:exclamation: try to do by next milestone)
- Gave review comments to other PRs (:exclamation: try to do by next milestone)
Merged updates to documents(:exclamation: try to do by next milestone)
arunbecoding.png uploaded and linked from AboutUs page, merged(:exclamation: try to do by next milestone)

Individual progress of @elsakoh for v1.1

Team repo forked to your GitHub account https://github.com/elsakoh/main (:heavy_check_mark: well done!)
Used forking workflow:
- Created PRs #5 (:heavy_check_mark: well done!)
- Gave review comments to other PRs (:exclamation: try to do by next milestone)
Merged updates to documents(:exclamation: try to do by next milestone)
elsakoh.png uploaded and linked from AboutUs page, merged(:exclamation: try to do by next milestone)

Individual progress of @gabrielseow for v1.1

Team repo forked to your GitHub account https://github.com/gabrielseow/main (:heavy_check_mark: well done!)
Used forking workflow:
- Created PRs #3 (:heavy_check_mark: well done!)
- Gave review comments to other PRs (:exclamation: try to do by next milestone)
Merged updates to documents(:exclamation: try to do by next milestone)
gabrielseow.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @seahlynn for v1.1

Team repo forked to your GitHub account https://github.com/seahlynn/main (:heavy_check_mark: well done!)
Used forking workflow:
- Created PRs #2 (:heavy_check_mark: well done!)
- Gave review comments to other PRs (:exclamation: try to do by next milestone)
Merged updates to documents(:exclamation: try to do by next milestone)
seahlynn.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Tutor: @junrong09

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-03 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

Assign-member command syntax in the Quick Start portion of the User Guide

I tried the assign-member ti/1 mi/AS command under the quick start section but it didn’t work. It looks like the syntax was updated sometime after the quick start section was written and the syntax in that portion of the user guide was overlooked. The updated command syntax works correctly so it’s probably just a matter of updating the Quick Start section of the user guide.

The first image shows the result of copying the assign member command from the quick start section of the user guide.

The second image shows that the command works with the updated syntax.

Medium severity since it is the example command given at the very start of the user guide.

_{[original: lyskevin/ped#1]}

Create a tag command that let's user give the same tag to multiple tasks/members

Wrong mapping of tn/ and im/ tags in section 3 of the user guide

The tn/ tag is mapped to image url and the im/ tag is mapped to task name in section 3 of the user guide. Looks like they should be swapped around.

_{[original: lyskevin/ped#3]}

Style all ui components

Member's name gets truncated if it is too long

A member's name gets truncated if it is too long. The fix should be pretty similar to the one in Duke where long commands/reponses were also getting truncated. A possible fix is to use the setWrapText method or the wrapText attribute in FXML.

_{[original: lyskevin/ped#2]}

The command `calendar` was stated in the user guide at the beginning, but it does not work.

The calendar command was then stated that it is to be released in v1.3, but it does not work.

_{[original: Kyzure/ped#1]}

As a project leader, I can add project members

As a project leader, I want to add tasks

Exporting inventory report

Task Name too long will provide an ellipsis instead of wrapping text

When adding a task, if the name is too long, it will appear as cut-off instead of provindg wrapping text. Users will not be able to see if the task appears too long.

_{[original: Kyzure/ped#3]}

As a project leader, I can create a meeting

User guide claimed to use dd/mm/yy when actually it is dd/mm/yyyy in the application

_{[original: Kyzure/ped#9]}

Settings to allow user to customsie +Work

In order of priority

Create a settings page, complete with labels of each setting that the user can customise (if possible will include toggle switches that are responsive to user's settings command)
Light/Dark theme switch
12/24 hour display format
Reminder scheduling for upcoming tasks (moved to 1.4)

Innacurate command results and UI caused by filteredLists

Since most of the data required for features is retrieved from the relevant filteredLists in Logic, e.g. filteredMembersList, the data is dependant on the current Predicate applied.

If user enters find-task nonsense, the filteredTaskList will be empty as nonsense doesn't exist. However this affects all components that are reliant on existing tasks. For example, if user enters assign-member ti/1 mi/JD, command result shown is Task id is not valid.

May need to restructure the way data is fetched for the UI.

Setting task deadline to the 29 of Feburary 2019 (Not leap year) will cause the task deadline to be 28 of Feburary 2019

This is the same for 29, 30 and 31 of Feburary, they can still be added but will be changed to 28 of Feburary.

_{[original: Kyzure/ped#10]}

Feedback on week 9 project progress for CS2103T-T12-1

Team progress for `v1.2`

Individual progress of @ambhinav for `v1.2`

Merged PRs that updated Java/FXML files during the past week e.g., #51 #13 #12 (:heavy_check_mark: well done!)
Has issues/PRs assigned for the v1.2 milestone #31 (:heavy_check_mark: well done!)

Individual progress of @ArunBeCoding for `v1.2`

Merged PRs that updated Java/FXML files during the past week e.g., #29 #26 #25 (:heavy_check_mark: well done!)
Has issues/PRs assigned for the v1.2 milestone #40 (:heavy_check_mark: well done!)

Individual progress of @elsakoh for `v1.2`

Merged PRs that updated Java/FXML files during the past week e.g., #53 #46 (:heavy_check_mark: well done!)
Has issues/PRs assigned for the v1.2 milestone ( ❗ )

Individual progress of @gabrielseow for `v1.2`

Merged PRs that updated Java/FXML files during the past week e.g., #52 #47 #18 (:heavy_check_mark: well done!)
Has issues/PRs assigned for the v1.2 milestone #40 (:heavy_check_mark: well done!)

Individual progress of @seahlynn for `v1.2`

Merged PRs that updated Java/FXML files during the past week e.g., #50 #49 #28 (:heavy_check_mark: well done!)
Has issues/PRs assigned for the v1.2 milestone #44 (:heavy_check_mark: well done!)

Tutor: @junrong09

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-17 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

Highly active tP noted -- Kudos!

Guys, it looks like your tP is maintaining a high-level of coding activities so far and all members are actively contributing (as per the tP Dashboard) 👍

Note: hope you can work together to help less-active team members, if they need help.

Keep up the good work!

Remove all references to address book in comments

Create test cases for AddTaskToMember and AddMemberToTask commands (for remove as well)

Create a get statistics function

Let's user view the workload and inventory distribution among members, as well as time taken for tasks.

Firing a member using `fire /ti [TASK_ID] /mi [MEMBER_ID] was able to fire it, but nothing happens and still appear under the task.

After firing it, it still appears under the task, and cannot be fired any more.

_{[original: Kyzure/ped#8]}

As a project leader, I can sync team members schedules

Allow user to import/export ics files
Parse all the member's calendars so that the user can schedule a meeting
Create a new meeting and display it on the dashboard (If there is no meeting yet, display accordingly}

Feedback on week 6 project progress for CS2103T-T12-1

Progress of this week

Team org and repo set up with the correct names
Product website available at the expected URL(:heavy_check_mark: well done!)
PR created from team repo to our repo(:exclamation: try to do by next milestone)

Individual progress of @ambhinav

Team repo forked to your GitHub account https://github.com/ambhinav/main (:exclamation: try to do by next milestone)
A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)
A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @ArunBeCoding

Team repo forked to your GitHub account https://github.com/arunbecoding/main (:exclamation: try to do by next milestone)
A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)
A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @elsakoh

Team repo forked to your GitHub account https://github.com/elsakoh/main (:exclamation: try to do by next milestone)
A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)
A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @gabrielseow

Team repo forked to your GitHub account https://github.com/gabrielseow/main (:exclamation: try to do by next milestone)
A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)
A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @seahlynn

Team repo forked to your GitHub account https://github.com/seahlynn/main (:heavy_check_mark: well done!)
A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)
A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Tutor: @junrong09

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-19 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

As a project leader who is keeping track of purchases, tag the inventory purchase to the member who bought it

As a project leader with many members and tasks, i want to find out which group members are working on a particular task

If task name is too long, it will cut off under the member lists

If task name is too long, it will cut off instead of wrapping text.

_{[original: Kyzure/ped#4]}

Remove or rename file '\'

Guys, you have a file named \ that is causing problems for RepoSense. The file doesn't seem to be serving any legitimate purpose. Please rename or remove it ASAP.

Given example for done-task is wrong in the application.

The given done-task given is as of the picture, however, what is required is a space between done-task and ti/1

_{[original: Kyzure/ped#5]}

Undo Redo Command works but not stated in the User Guide and not shown in autocomplete.

_{[original: Kyzure/ped#12]}

Wrap up +Work

Need to fully wrap up the project

Code Quality
UG
DG

Dashboard: tasks, deadline and meetings

Full test Case
Code Quality
UG
DG

Calendar

Full test Case
Code Quality
UG
DG

Inventory

Full test Case
Code Quality
UG
DG

Enhancememts

Implement parser support for member-related commands

Enhance addTaskToMember so that you can add multiple tasks to the same member at once

Vice versa for addMemberToTask

As a project leader, I can view my next meeting in the home page

Feedback on week 11 project progress for CS2103T-T12-1

Team progress for `v1.3`

Milestone v1.3 managed systematically
- A suitable deadline set [2019-10-30] (:heavy_check_mark: well done!)
- All issues in it are closed (:exclamation: try to do by next milestone)
- Milestone closed (:exclamation: try to do by next milestone)
Build passing (checked at this commit, based on the build history reported by Travis) (:heavy_check_mark: well done!)
A new jar file has been released in the last 7 days (:heavy_check_mark: well done!)
User Guide updated in the last 7 days (:heavy_check_mark: well done!)
Ui.png updated in the last 7 days(:exclamation: try to do by next milestone)

Individual progress of @ambhinav for `v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #64 #38 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past 2 weeks e.g., #87 #84 #81 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past 2 weeks e.g., #83 #79 #76 (:heavy_check_mark: well done!)
Ensured the code is RepoSense-compatible and the tP dashboard is showing your code correctly (:question: tick this yourself after completing the item)

Individual progress of @ArunBeCoding for `v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #39 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past 2 weeks e.g., #71 #62 #61 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past 2 weeks e.g., #71 (:heavy_check_mark: well done!)
Ensured the code is RepoSense-compatible and the tP dashboard is showing your code correctly (:question: tick this yourself after completing the item)

Individual progress of @elsakoh for `v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #88 #75 #43 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past 2 weeks e.g., #86 #53 #74 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past 2 weeks e.g., #74 (:heavy_check_mark: well done!)
Ensured the code is RepoSense-compatible and the tP dashboard is showing your code correctly (:question: tick this yourself after completing the item)

Individual progress of @gabrielseow for `v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #43 #42 #33 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past 2 weeks e.g., #89 #80 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past 2 weeks e.g., #89 #69 (:heavy_check_mark: well done!)
Ensured the code is RepoSense-compatible and the tP dashboard is showing your code correctly (:question: tick this yourself after completing the item)

Individual progress of @seahlynn for `v1.3`

Has issues assigned or PRs authored for the v1.3 milestone #68 #58 #57 (:heavy_check_mark: well done!)
Merged PRs that update Java/FXML files during the past 2 weeks e.g., #77 #70 (:heavy_check_mark: well done!)
Merged PRs that update the Developer Guide files during the past 2 weeks e.g., #70 (:heavy_check_mark: well done!)
Ensured the code is RepoSense-compatible and the tP dashboard is showing your code correctly (:question: tick this yourself after completing the item)

Tutor: @junrong09

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-31 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

Enhance all addcommands to include assigning task/member right from the start

Enhance all add commands to support adding multiple tasks/members

Will do for both addtask and addmember

Feedback on week 8 project progress for CS2103T-T12-1

Team progress for mid-v1.2

Mid-milestone progress reports are FYI only. They are not graded.

Individual progress of @ambhinav for mid-v1.2

Merged PRs that updated Java/FXML files during the past week e.g., #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 #8 (:heavy_check_mark: well done!)
Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @ArunBeCoding for mid-v1.2

Merged PRs that updated Java/FXML files during the past week e.g., (:exclamation: try to do by next milestone)
Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @elsakoh for mid-v1.2

Merged PRs that updated Java/FXML files during the past week e.g., (:exclamation: try to do by next milestone)
Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @gabrielseow for mid-v1.2

Merged PRs that updated Java/FXML files during the past week e.g., (:exclamation: try to do by next milestone)
Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Individual progress of @seahlynn for mid-v1.2

Merged PRs that updated Java/FXML files during the past week e.g., (:exclamation: try to do by next milestone)
Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Tutor: @junrong09

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-10 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

ay1920s1-cs2103t-t12-1 / pluswork Goto Github PK

pluswork's Introduction

+Work

Site Map

Acknowledgements

Licence : MIT

pluswork's People

Contributors

Watchers

Forkers

pluswork's Issues

Team progress for mid-v1.3

Individual progress of @ambhinav for mid-v1.3

Individual progress of @ArunBeCoding for mid-v1.3

Individual progress of @elsakoh for mid-v1.3

Individual progress of @gabrielseow for mid-v1.3

Individual progress of @seahlynn for mid-v1.3

Team progress for v1.1

Individual progress of @ambhinav for v1.1

Individual progress of @ArunBeCoding for v1.1

Individual progress of @elsakoh for v1.1

Individual progress of @gabrielseow for v1.1

Individual progress of @seahlynn for v1.1

Team progress for v1.2

Individual progress of @ambhinav for v1.2

Individual progress of @ArunBeCoding for v1.2

Individual progress of @elsakoh for v1.2

Individual progress of @gabrielseow for v1.2

Individual progress of @seahlynn for v1.2

Progress of this week

Team progress for v1.3

Individual progress of @ambhinav for v1.3

Individual progress of @ArunBeCoding for v1.3

Individual progress of @elsakoh for v1.3

Individual progress of @gabrielseow for v1.3

Individual progress of @seahlynn for v1.3

Team progress for mid-v1.2

Individual progress of @ambhinav for mid-v1.2

Individual progress of @ArunBeCoding for mid-v1.2

Individual progress of @elsakoh for mid-v1.2

Individual progress of @gabrielseow for mid-v1.2

Individual progress of @seahlynn for mid-v1.2

Recommend Projects

Recommend Topics

Recommend Org

Jobs

Team progress for mid-`v1.3`

Individual progress of @ambhinav for mid-`v1.3`

Individual progress of @ArunBeCoding for mid-`v1.3`

Individual progress of @elsakoh for mid-`v1.3`

Individual progress of @gabrielseow for mid-`v1.3`

Individual progress of @seahlynn for mid-`v1.3`

Team progress for `v1.2`

Individual progress of @ambhinav for `v1.2`

Individual progress of @ArunBeCoding for `v1.2`

Individual progress of @elsakoh for `v1.2`

Individual progress of @gabrielseow for `v1.2`

Individual progress of @seahlynn for `v1.2`

Team progress for `v1.3`

Individual progress of @ambhinav for `v1.3`

Individual progress of @ArunBeCoding for `v1.3`

Individual progress of @elsakoh for `v1.3`

Individual progress of @gabrielseow for `v1.3`

Individual progress of @seahlynn for `v1.3`