nus-cs2103-ay2324s2 / pe-dev-response Goto Github PK

Description

Able to add 2 persons with the same email and phone number, which would not occur in real life.

Steps to recreate

1. Execute these commands
   addp n/David p/98987676 e/[email protected] a/NUS
addp n/Mary p/98987676 e/[email protected] a/NUS

Expected

Both persons are added to the address book.

Actual

A message stating that the user with the same number and email already exists in the address book.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#7] [original labels: severity.Low type.FeatureFlaw]}

Tested: reschedule 8 s/32-06-2024T16:00
Expected: User reschedules the starting time only
Actual: User Guide specifies At least one of the optional fields must be provided. but later says that start time must be accompanied by end time. Users should be able to edit either one of the timings as meetings can be delayed or started earlier than expected.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#28] [original labels: severity.Low type.FeatureFlaw]}

Description

When the app is first opened, and the user types in the deselect command, the command works, and the command box displays 'Event deselected', event though no event is selected, as shown in the event participation list.

Steps to recreate

1. Launch app
2. Execute desel command

Expected

A message stating that no event has been selected.

Actual

A message stating that event has been deselected.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#6] [original labels: type.FunctionalityBug severity.Low]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Missing glossary for Meeting (i.e., Information on a scheduled meeting, including date, time and notes for TODAY's DATE ).

Upon one glance, the users have no idea that only meetings scheduled for TODAY will be displayed.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#52] [original labels: severity.Medium type.DocumentationBug]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Data integrity is a phrase that appears often in the UG but is not explained in the glossary. This is quite a difficult term to understand for an average user, so it would be very useful to add into the glossary

---

_{[original: nus-cs2103-AY2324S2/pe-interim#21] [original labels: type.DocumentationBug severity.VeryLow]}

---

_{[original: nus-cs2103-AY2324S2/pe-interim#2] [original labels: type.FunctionalityBug severity.Medium]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Phone is an optional in Person, should be 0..1 multiplicity.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#56] [original labels: type.DocumentationBug severity.VeryLow]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Justification: Not enough screenshots provided for users to see the expected execution of the commands

---

_{[original: nus-cs2103-AY2324S2/pe-interim#47] [original labels: type.DocumentationBug severity.VeryLow]}

Expected: To display FINDvisor as the application name

Actual: The data files and application shows the old addressbook title

---

_{[original: nus-cs2103-AY2324S2/pe-interim#23] [original labels: type.FeatureFlaw severity.VeryLow]}

Description

When the name and phone number of the participants are exported, the title says 'exported_partici'.

Steps to recreate

1. Execute the export n/ p/ command with at least one participant in the address book.
2. Open the .csv file

Expected

A suitable title, such as Exported participants

Actual

A title that says 'exported_partici'

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#12] [original labels: type.FeatureFlaw severity.VeryLow]}

The find command only supports name and tags. However, there are 7 different types of prefix available in the program, including both events and persons.

I think it would be great if the application could support more prefixes for a better user experience.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#62] [original labels: severity.Low type.FeatureFlaw]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Description

There is no clear indication that the Orange/Yellow background color means that the user has selected that particular event in the User Guide. The user is made to assume this information.

Screenshot

---

_{[original: nus-cs2103-AY2324S2/pe-interim#14] [original labels: type.DocumentationBug severity.VeryLow]}

Tested: help
Justification: Pops up a seperate window that covers the actual application. User has to use a mouse to close the menu which is not ideal for someone who prefers to type

---

_{[original: nus-cs2103-AY2324S2/pe-interim#30] [original labels: severity.Low type.FeatureFlaw]}

Tested: edit 6 n/123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567

Justification: Pure numeric input should not be considered as a valid name input. This is against the standard norm

---

_{[original: nus-cs2103-AY2324S2/pe-interim#46] [original labels: type.FunctionalityBug severity.Low]}

The error message shown when using export when the file name does not follow the conventions according to the UG (where the only special characters allowed are - and _) does not tell the user what went wrong which is likely to leave users confused

Error recreation: export f/../file

---

_{[original: nus-cs2103-AY2324S2/pe-interim#15] [original labels: type.FunctionalityBug severity.Low]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

PersonCard should be directly below PersonListPanel and not MeetingCard. The current diagram is confusing

---

_{[original: nus-cs2103-AY2324S2/pe-interim#36] [original labels: severity.Low type.DocumentationBug]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

While the method shows that it self invokes

But here we are finding the email through the model

---

_{[original: nus-cs2103-AY2324S2/pe-interim#4] [original labels: severity.Low type.DocumentationBug]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Tag does not allow white spaces under the t/ parameter, I think this should be specified in the UG since it is specified for KEYWORD

---

_{[original: nus-cs2103-AY2324S2/pe-interim#26] [original labels: type.DocumentationBug severity.VeryLow]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

---

_{[original: nus-cs2103-AY2324S2/pe-interim#5] [original labels: severity.Low type.DocumentationBug]}

Cut off, cannot scroll as well. Affects usage as i cannot see the group name once i group them together, so theres no point

---

_{[original: nus-cs2103-AY2324S2/pe-interim#44] [original labels: severity.Medium type.FeatureFlaw]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Seems like withing is meant to be within

---

_{[original: nus-cs2103-AY2324S2/pe-interim#31] [original labels: type.DocumentationBug severity.VeryLow]}

Users should be able to edit an application if they mistakenly put in the wrong email.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#3] [original labels: severity.Low type.FeatureFlaw]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

This violates the single-user constraint for the TP

---

_{[original: nus-cs2103-AY2324S2/pe-interim#33] [original labels: severity.Low type.DocumentationBug]}

Tested: edit 1 1 n/Test1
Expected: Error message should specify that edit only accepts 1 index parameter.
Actual: The same invalid command error is raised for any possible wrong input. Hinders user ability.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#24] [original labels: type.FeatureFlaw severity.VeryLow]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

There should be 1 at the arrow heads near Name, Phone, Address, Email as these are compulsory fields to define a Person.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#37] [original labels: severity.Low type.DocumentationBug]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Meeting records cannot be found through find command unlike what the DG specifies.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#57] [original labels: severity.Low type.DocumentationBug]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Description

There are no screenshots in the export command section of the User guide that shows the user what the .csv that has been exported will look like.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#17] [original labels: type.DocumentationBug severity.VeryLow]}

Most command such as in the above example "tag" require the user to the specify the student via their student ID. The student ID consists of 9 characters following a specific format. This requirement is quite a hassle for the user and may slow down their efficiency when using EduLink.

The page already has numbering for each student, perhaps could allow the user to specify by the numbering for each student as well such as "1" for Alex Yeoh as shown in the screenshot

---

_{[original: nus-cs2103-AY2324S2/pe-interim#19] [original labels: severity.Low type.FeatureFlaw]}

Steps to reproduce

1. Select an event with the sel command.
2. Deselect the event with the desel command.

Expected

The event should have a background that matches the rest of the UI (blue in this case since the colors are alternating between blue and green)

Actual

The event background is gray

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#8] [original labels: type.FeatureFlaw severity.VeryLow]}

The UG states that the command format for the add command is:
add n/NAME id/STUDENT_ID p/PHONE_NUMBER e/EMAIL a/ADDRESS in/INTAKE m/MAJOR

While the error message shows the format as:
add id/STUDENT_ID n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS m/MAJOR in/INTAKE

Just a documentation error as it seems the command works regardless of order of inputs

---

_{[original: nus-cs2103-AY2324S2/pe-interim#22] [original labels: severity.Low type.DocumentationBug]}

Tested: edit 8 t/PneumonoultramicroscopicsilicovolcanoconiosisPneumonoultramicroscopicsilicovolcanoconiosisPneumonoultramicroscopicsilicovolcanoconiosis

Expected: Display the tag as-is or raise an error to limit the length of tag a user can provide

Actual: Tag output cut off in UI, users unable to scroll or view the entire tag

---

_{[original: nus-cs2103-AY2324S2/pe-interim#45] [original labels: type.FeatureFlaw severity.VeryLow]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Justification: No user story available for add command although it is the most crucial and fundamental command within the application

---

_{[original: nus-cs2103-AY2324S2/pe-interim#48] [original labels: severity.Low type.DocumentationBug]}

After executing import with a separate json file that also features Alex Yeoh:

---

_{[original: nus-cs2103-AY2324S2/pe-interim#16] [original labels: type.FunctionalityBug severity.Medium]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Should replace AddressBook with the name of your application

---

_{[original: nus-cs2103-AY2324S2/pe-interim#50] [original labels: type.DocumentationBug severity.VeryLow]}

Tested: schedule 8 s/30-02-2025T16:00 e/31-04-2025T17:00 mr/test
Expected: Raise a specific error that invalid dates have been provided
Actual: Vague error message, frustrating the users who have no idea why the application is not accepting the input

---

_{[original: nus-cs2103-AY2324S2/pe-interim#27] [original labels: severity.Low type.FeatureFlaw]}

Description

Executing the clear command doesn't delete entries from the event participation list.

Steps to reproduce

1. Ensure there are events with participants present, and some participants in the global participant list.
2. Execute the clear command.

Expected

Participants in the events to be deleted.

Actual

Participants in the events are still present after the clear command was executed.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#13] [original labels: severity.Low type.FeatureFlaw]}

Tested: edit 9 n/Test2 when initial name was Test2
Expected: Raise an error that the same name value was given
Actual: Accepted the edit command, confusing for users

---

_{[original: nus-cs2103-AY2324S2/pe-interim#34] [original labels: type.FunctionalityBug severity.VeryLow]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Under 3.2.4 Editing existing participant: editp:

---

_{[original: nus-cs2103-AY2324S2/pe-interim#11] [original labels: type.DocumentationBug severity.VeryLow]}

Justification: Error should display that invalid date has been provided, and not that there is an issue with specifying start and end dates in an order. Vague error message that is unintuitive for users.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#29] [original labels: type.FunctionalityBug severity.Low]}

Description

Able to add dates like 01-01-0001

Steps to reproduce

Execute the following command - addev ev/Party d/01-01-0001

Expected

A error stating that the date is invalid.

Actual

Event is added.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#9] [original labels: severity.Low type.FeatureFlaw]}

When tag is too big and overflows, scrolling of the name cards is not allowed, and all information is displayed in a bigger card. I dont think this inconsistency is documented, so ill just put it here. For examplem, address is cut off in the example below as the line is too long and scrolling is disabled

---

_{[original: nus-cs2103-AY2324S2/pe-interim#49] [original labels: type.FeatureFlaw severity.VeryLow]}

The add command thinks that tags are not alphanumeric but it is actually adding an invalid tag

---

_{[original: nus-cs2103-AY2324S2/pe-interim#1] [original labels: type.FunctionalityBug severity.Low]}

When editing or deleting the tag, the user is required to fully type out the tag that can be up to 20 characters long. This creates room for error and mistakes by the user as it difficult to quickly type out 20 characters accurately, slowing down the efficiency of using EduLink.

Could perhaps number each tag instead and allow users to make edits and deletes by just specifying the tag number.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#18] [original labels: severity.Low type.FeatureFlaw]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Description

Some command summaries have full stops while others don't.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#10] [original labels: type.DocumentationBug severity.VeryLow]}

Tested: edit n/Zoé / edit 9 n/Krishnan s/o helloworld
Expected: Accepted as a valid name as accented names and 'S/O' or 'D/O' are common
Actual: An error was raised

---

_{[original: nus-cs2103-AY2324S2/pe-interim#35] [original labels: type.FunctionalityBug severity.Low]}

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Description

The UML diagram in the Developer guide shows that the Event model has a EventName associated with it, but it doesn't have a Date, which is present in the application.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#20] [original labels: type.DocumentationBug severity.VeryLow]}

Tested: test@example
Expected: Raise error that invalid email is provided
Actual: Accepted and edited the person detail with an invalid email

---

_{[original: nus-cs2103-AY2324S2/pe-interim#38] [original labels: type.FunctionalityBug severity.Low]}

Tested: deletetag 6 t/DavidGf and deletetag 6 t/DavidGirlFriend

Justification: The output shows the internal data structure of tag (i.e. [[...]]) when it should be a pure textual output

---

_{[original: nus-cs2103-AY2324S2/pe-interim#32] [original labels: type.FeatureFlaw severity.VeryLow]}

After executing tag t/VeryNiceGuy:

This is quite a big flaw as usually separate json files are kept to contain different information, however upon updating the information once, all the json files will have the same information. This also happens when adding new students as well.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#25] [original labels: type.FunctionalityBug severity.High]}

Command format is valid but not valid index

---

_{[original: nus-cs2103-AY2324S2/pe-interim#53] [original labels: type.DocumentationBug severity.VeryLow]}