You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be nice to have different error prompts for different errors so that the user knows what he is doing wrong
As can be seen below, it throws me the same error be it wrong date format(dd/mm/yyyy instead of dd-mm-yyyy), wrong timing(2160 2161) and invalid start/stop timing(2100 2059)
The text was updated successfully, but these errors were encountered:
The severity should be Low, since this is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.
Excepts to end before start exception at a incorrect place, and reschedule input format wrong message does not show correctly.
Items for the Tester to Verify
❓ Issue severity
Team chose [severity.Low].
Originally [severity.High].
I disagree
Reason for disagreement: [replace this with your reason]
❓ Issue type
Team chose [type.FunctionalityBug].
Originally [type.FeatureFlaw].
I disagree
Reason for disagreement: [replace this with your reason]
I think it would be nice to have different error prompts for different errors so that the user knows what he is doing wrong
As can be seen below, it throws me the same error be it wrong date format(dd/mm/yyyy instead of dd-mm-yyyy), wrong timing(2160 2161) and invalid start/stop timing(2100 2059)
The text was updated successfully, but these errors were encountered: