nus-pe-script
commented
4 days 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]
Team's Response
I acknowledge this is a valid functionality bug as our implementation doesn't match what's documented in the UG regarding email validation rules. However, I would like to suggest downgrading the severity from Medium to Low because:
- This only affects a very specific edge case - emails containing exactly two consecutive underscores
- Single underscores work as expected (e.g., 'a_a@example.com' is accepted)
- This appears only in rare situations as double underscores in email addresses are uncommon in regular usage
- There's a simple workaround of using single underscores instead
- The limitation doesn't prevent users from performing any core functionality of the application
- Most users would still be able to use their regular email addresses without issue
While we agree this is a bug that should be fixed to fully match our documented rules, its impact on regular usage is minimal enough to warrant Low severity classification.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Description:
According to the user guide, the local part of the email is valid as long as it follows the following rules:
Based on the validation rules above,
a__ashould be a valid local part. However, when attempting to enter any email witha__aas the local part, the application shows an error stating that the email format is incorrect.Steps to reproduce:
Enter the following command:
An error stating that the email has an invalid format will be displayed.