Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Screenshot for Adding Schedule #13

Open
HusseinSafwan02 opened this issue Apr 19, 2024 · 1 comment
Open

Missing Screenshot for Adding Schedule #13

HusseinSafwan02 opened this issue Apr 19, 2024 · 1 comment

Comments

@HusseinSafwan02
Copy link
Owner

HusseinSafwan02 commented Apr 19, 2024

Adding a schedule is a non-trivial command, so screenshots would be greatly useful for the user.

Currently, there are no screenshots for this non-trivial command:

image.png

It is expected that users would have a screenshot to refer to.

@nus-se-bot
Copy link

nus-se-bot commented Apr 22, 2024

Team's Response

We reject this bug. The reasons are as follows:

  • Screenshots are not strictly necessary to help the user.

  • Screenshots are a cosmetic issue and should, at the very maximum, have "Very Low" severity.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

  • I disagree

Reason for disagreement: Missing screenshots are not cosmetic, as screenshots are necessary so that the reader can refer to the intended response of the application once a command is used. While for some simple commands it is not necessary to include screenshots as the command may be straightforward/not affect the key functionalities of the application, the add command in this case is a major feature of the application. It is thus a bug that a screenshot for this command is not included, especially since many other commands in the UG so not have screenshots as well.


❓ Issue severity

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

  • I disagree

Reason for disagreement: Since the add command is a key feature of the application, it is important to have screenshots of its use so that users are able to refer to the expected response when the command is used.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants