the output does not match the user guide. Moreover, this issues occurs for every command since the INFO: ____ and the date, time and command class appears for everything but not in the user guide

[nikhil-2101]

[soc-se-bot]

Team's Response

We believe this is a cosmetic error that will not hinder usage or function of programme, hence we believe the severity is more accurately reflected as very low than the proposed high.

The 'Original' Bug

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

Appearance of logging statements

There is the constant appearance of logging statements in the programme, which is extremely distracting and confusing for the user, who has no need at all for such logging statements which were meant for developers. This will add unncessary lines to the code interface and require a larger screen than necessary and will distract users from the task at hand.

However, given that this does not affect user usage but distracts them, I shall give this a functionality bug a severity of low.

---

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

Their Response to the 'Original' Bug

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

Pure cosmetic design choice, hence it is downplayed to very low.

This should not affect UI/UX to the suggest degree at all, since there is only one line of logging statements each time they appear. While it should be removed for cosmetic reasons, the slight appearance of miniscule logging statements should not affect user experience at all.

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: [replace this with your explanation]

---

❓ Issue severity

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

• I disagree

Reason for disagreement: The reason this was put as high as this output is extremely off-putting to see when using the application. Realistically, a user would not want to see eg. Apr 19 2024 4:35:18 PM classify.commands.ArchiveCommands getStudent every time the method is called. The repeated viewing of these messages could frustrate users in the long term and could possibly deter them to want to use this. While it may seem that cosmetic reasons are considered to be of VeryLow severity for you, it is actually of High severity for actual users due to the fact that unnecessary outputs such as this have to be seen for every command used, thus annoying them.

---