Open sebin0817 opened 2 months ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Thank you for the bug report.
We have decided to mark the bug report as not in scope.
We have addressed a similar feature flaw in our planned enhancements, which is to throw an error on which specific field is failing.
However, we decided that the separation of differentiating between invalid format and invalid value is not in scope as we feel that the planned enhancement will be more helpful by narrowing down to a specific parameter and that the separation of differentiating between invalid format and invalid value should come after this enhancement.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your reason]
Tested:
schedule 8 s/30-02-2025T16:00 e/31-04-2025T17:00 mr/test
Expected: Raise a specific error that invalid dates have been provided Actual: Vague error message, frustrating the users who have no idea why the application is not accepting the input