Skip to content

(Error notifications available) For input errors, "name of the field in error" must be part of the problem description #669

@RashmiKatakwar

Description

@RashmiKatakwar

Make sure that the following need is covered in the requirement/requirement description.

When there is an input error, the error message must include the name of the field where the error occurred.
If error message is too generic and do not specify the field, it can make it harder for people with cognitive disabilities to understand and fix the issue.

Error messages like:

  • “This field cannot be empty”
  • "Enter value greater than 18"

do not clearly indicate which field has the error.

Error messages should clearly mention the field name, for example:

  • "Last name cannot be empty"
  • "Age can not be less than 18"

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions