...so that I can update member information to latest

1. Locating persons by name: find n/KEYWORD [MORE_KEYWORDS]
2. Locating persons by phone: find p/KEYWORD [MORE_KEYWORDS]

...so that I can easily analyze the members’ consumption and distribution.

Related Link

Related Link

Command lists add -m as the command to add a member instead of add -mem

Labels: type.DocumentationBug severity.Low
original: Smanmos/ped#1

... so that I can easily view and access the member basic information.

... so that I can easily find the specific members to check their details.

... so that I can easily check how to use the commands and access the user guide.

Share 2-3 screenshots you took while at various points of the tutorial Tutorial 1 - Tracing a Command Execution Path

Related Link

...so that I can easily offer promotions to the members with the highest consumption.

...so that I can remove member that I no longer need.

• no error message shown when adding transaction to a member whose id doesn't exist
• when adding multiple transactions at the same time, (eg. add -t 123.00 -t 1234.00 -id 00001), the amounts show up at the bottom, but doesn't show up when adding a single transaction (eg. add -t 123.00 -id 00001)
  

... so that I can easily find the specific member to check his/her details.

... so that I can easily view and access the member contacts

Links

I set up the milestones on our tp in origination, remember to check the deadline for each milestone.
We only can implement functions during v1.2 and v1.3. (Now is v1.1)
https://github.com/AY2122S1-CS2103T-F12-4/tp/milestones

I set up the labels for our issues and pull requests on our tp in origination
https://github.com/AY2122S1-CS2103T-F12-4/tp/labels

Project Folder
https://drive.google.com/drive/u/1/folders/1SNXqTZQa648i7KS61EjxL44xXK8gTx21

Project functions implementation:

1. Fork the project to your personal github account
2. Create issue to represent project tasks at origination repo for the function that you are going to implement (add the link, add milestones, projects, at the right side of the issue page)
3. Create a pull request to our tp in origination: https://github.com/AY2122S1-CS2103T-F12-4/tp for the function at step 2
   a. Tag your pull request type
   c. Link this pull request to the issue at step 2 (add the link, milestones at the right side of the pull request page)
   c. add key word like "close""fix", etc. at your pull request description
4. Implement functions at a separate branch of your local repo, branch name start with "branch-"

Notes:

1. Try to implement test cases for each of your new functions as many as possible, try to cover 90% functions (From prof expectation)
2. Try to minimum the size of each commit
3. All the ready pull request should be bug fix
4. Follow the comment style and code style like iP
5. Bug free is most important key point in tP, our PE is highly related to this
6. New updating need to be implemented at a separate branch of your local repo
7. All of us can do code review for all the pull requests
8. If there are any request is ready just @HolmesJJ or @zzybluebell at your pull request description or telegram
9. Keep pulling the latest version of the master

Todo:

• Plan who is going to implement which features
• Plan the next iteration Link
• Check whether the reservations that have expired need to be marked
• Check whether the current data need to be back up when clearing the program (UG)
• Update the hyperlink of the GitHub logo on the upper left corner
• Update the home page Link
• Divide documentation work among team members equally; preferably based on enhancements/features each person would be adding (Add your name below the feature if your added this feature) Link
• check addressbook keywords in the whole project
  • address book
  • addressbook
  • addressbook ab
  • ab
  • ab-3
  • address-book
  • addressbook.json
  • addressbook-level3
• check all the hyperlink to make sure they are not broken
• seedu.address, person -> member
• add member need to check the member id is full
• add json description (UG)
• run test coverage report
• Need to fix one bug for the transaction, using set will cause comparing errors for the different transaction objects with the same amount. And this is not the proper way to add transactions and calculate the sum, need to check if the sum will overflow.
• update -> edit; search -> find
• reservation time should be future time (UG)
• fix AddCommandPrefixParser parse
• error message for billing, credit, point, etc should be positive number
• run add -txn -b 1.00 -id 10002 after find -m -id 10001 will throw error
• beautify UI
• Some issues:
  • Transaction
  • AddCommand
  • requireNonNull
  • createUpdatedCredits
  • assert
  • updatedBilling
  • import seedu.address.model.reservation.Id;
  • Add Reservation at the same day
• When delete transaction point performance
• Adding a member : add -mem/
• Show that phone email id cannot be replied (UG)
• Big integer
• different language (UG)
• remove page feature (UG)
• Update the MainWindows don't show all member details
• You can reach us via email, as indicated below. (About)
• code quality for summary
• max billing, credit, point, number of member, transaction, reservation, index number (UG)
• Only one reservation can be added within the same day
• keyword not including prefix (UG)
• point will be made up if gaven less, deduct if gaven more (UG)
• Update UI.png
• id 10001100001 (UG)
• HD Logo (UG)
• update HelpWindow content
• update readme and ug image
• same member cannot have multiple reservations in the same day
• help box member id tran id
• find can be multiple keywords (UG)
• esc exit window (UG)
• Update a password -> Set Password (UG)
• summary Add, Delete Reservation, Reservation space, all edit delete Reservation id front (UG)
• Point 4 maybe need another screenshot for the first launch (UG)
• retrieve commands up to 30 records (UG)
• Seat Booking Information should be coming (UG)
• Requirements of input command bold and can be warning box, ONLY USED IN SORT COMMAND no need to upper case and it is too big (UG)
• English language based user can bold (UG)
• redeem -f (UG)
• start from 00001
• full stop
• sort -mem/ -c/ -a/
• icon lowcase
• user? staff?
• send email to us (UG)

... so that I can prevent staff from accessing manager-only features.

... so that I can easily find the specific member to check his/her details.

In the feature heading, it clearly stated the command to be add -m but in the example given, it seems that the actual command is add -mem.

I was thinking it might be a shortcut but it does not seem to work.
This is most likely a documentation bug.

Labels: type.DocumentationBug severity.Low
original: CheongYeeMing/ped#1

... so that I can easily find specific members to check their details.

... so that I can easily track the member statuses.

...so that I can access manager-only features, e.g. modify the membership level.

... so that I can easily track the member statuses.

when adding a new duplication bill, should be added in transaction List

... so that I can easily check the specific member's details.

Related Link

Related Link

Update new features and add UML diagrams

Copy pasted the 'add -mem-n John Doe -p 98765432 -e [email protected] -a 112 Amoy Street, 069907, Singapore' command into the command box and it there me an Invalid command format error.

Labels: type.DocumentationBug severity.Low
original: itsraveen/ped#1

... so that I can easily find specific member to check his/her details.

Features such as find and edit are broken down to too many fields which clutter up the main contents table.
It makes it harder to get a fast grasp of all the available commands. I suggest these sub-headings be removed from the contents.

Labels: type.DocumentationBug severity.Low
original: vimuthm/ped#1

... so that I can easily track the transaction history of members.

Detailed information has been moved into ViewWindow.