Open ruiyangzh opened 10 months ago
Since this issue mentions two bugs:
We choose the first bug to discuss.
We downgrade the severity of this bug to severity.Low
since it only inconveniences the user occasionally, as only a subset of schedules a user wishes to key in will lack fields.
Moreover, we mark this bug as response.NotInScope
since:
YYYY-MM-DD-HH-mm
is accepted.note
was better spent towards those features, rather than tweaking a facet of a feature that causes minor inconvenience. Team chose [response.NotInScope
]
Reason for disagreement: Hi, I can see the reasoning for this being not a medium-severity bug. However I still think this should be considered a bug to be fixed. The problem is not that the user is unsure when the meeting is; it's that the user must provide additional details even when such details are not necessary to their workflow, and burdens them to type extra strokes, especially the '-' character which is a special character. Although this is stated in the UG, I do not believe that much extra effort would be needed.
The command format requires user to key in details of a meeting's timing down to the minute. This is not only unneccessary (as many schedules may not be a strict timing), but also frustrates the user when entering a schedule since the reason for failure is not informed to the user. For example the command
schedule 1 i/2021-02-29-23-23
are rejected because they do not fit the leap year timings.However, the message is a generic
This can affect users quite severely, since meetings are a core feature of the application. However the app is still useable, hence it is of severity medium.