Team's Response

We have rejected this issue as we have provided an example for a valid date both in the error messages as well as in the UG.

Additionally, as per Java documentation, each letter and its specific casing has a representation for a certain time element as seen in the screenshot below. The casing should hence not be uniform throughout all formats. For instance, upper case MM in dd-MM-yyyy represents 2 digits for the month of the year whereas lower case 'mm' represents the 2 digits for the minute of the hour. We have tasks which can have deadlines and we have stated in both the UG and in the application that task deadlines follow the dd-MM-yyyy HHmm format. As you can see, capitalization matters here since we use both MM and mm to represent month and minutes respectively and in accordance to the Java documentation. So, to prevent confusion for users who are knowledgeable regarding date-time formats, it should NOT be "DD-MM-YYYY or dd-mm-yyyy instead to make it more consistent" as wanted by the tester.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

[x] I disagree

Reason for disagreement: While this is true for Java documentation, your target audience (who I assume are people handling projects) may not have knowledge of Java and hence may not know about Java documentation.

I searched on Google and found that most websites either used all-caps or no-caps (as shown below).

To make it more understandable for your audience, I think that you should use either all-caps or no-caps. I believe that this still qualifies for a severity.VeryLow as it is can be fixed easily by changing the capitalisation.

Weiennn / pe

The DD-MM-YYYY format is not consistent for editP error message #4

Team's Response

Items for the Tester to Verify

:question: Issue response