Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Screenshots under edit task not sufficient to show edits

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 include before -after comparison, similar problem for other edit features

---

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

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

The details for the edit task command and other edit commands are already specified in words above the screenshot. The missing screenshot does not affect the functionality of the UG as users can still use the command even without any of the screenshots.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: I disagree that they are duplicates as the module website mentioned that bugs can only be marked as duplicates if they CANNOT be fixed independently. In this case, the 2 bugs above are from different features of the UG, and must be fixed independently, thus these 2 bugs are not duplicates.

❓ Issue severity

Team chose [severity.VeryLow]
Originally [severity.Low]

• I disagree

Reason for disagreement: This is not purely cosmetic as this section is essentially guiding users on how to use certain commands in the application. Without sufficient and proper screenshots, the user will not be able to visualise the expected changes and validate if what they are doing is correct. As mentioned in the module website, the lack of visuals and poor integration of visuals into explanation is a bug. Thus I stand by the original severity of Low.

from pe.