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
After trying to sort the list with different parameters I realised that the success message for all is the same and it might be a little confusing since you might not know which field the list was sorted by?
Success message shown below:
The text was updated successfully, but these errors were encountered:
Thank you for your input. We could have improved this in a further iteration, but we believe that it is currently not in scope. In addition, users can use the history command to check what they sorted the list by.
Items for the Tester to Verify
❓ Issue response
Team chose [response.NotInScope]
I disagree
Reason for disagreement: While I agree that it should be a feature flaw, I believe that it should be Accepted instead of NotInScope. Based on the course website, for a feature flaw to be considered as not in scope, it should be of lower priority and require greater effort to implement.
However, I believe that it would require little effort to just add the field being sorted by in the error message and hence should be Accepted rather than NotInScope.
❓ Issue type
Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]
I disagree
Reason for disagreement: [replace this with your explanation]
After trying to sort the list with different parameters I realised that the success message for all is the same and it might be a little confusing since you might not know which field the list was sorted by?
Success message shown below:
The text was updated successfully, but these errors were encountered: