Content
View differences
Updated by Marc Alcobé 12 months ago
#### Acceptance criteria
* In all forms in the application, do not deactivate the "Save" button.
* If the user taps on the "Save" button but there are errors in the form, trigger inline errors below the pertinent field.
* The inline errors might be:
* Mandatory field missing: "This is a mandatory field. Please, fill the required information".
* Wrong field format: "The information provided doesn't match the format of this field".
* Any other error: "An error occurred with this field. Please, try again later"
* Empty comment box: "It is not possible to add an empty comment".
* When an inline error appears, ensure that the view navigates to the place where the faulty field is displayed (e.g. when the field is in a tab of the work package form not opened).
* If there is more than one error, the user will jump from a faulty field to the next when tapping in the "Save" button.
> ## Bug report:
>
> ##
>
> ### Steps to reproduce
>
> 1. Open a work package creation page
>
> 2. Don't fill in all mandatory fields and try to save
>
>
> ### What is the buggy behavior?
>
> * Save is disabled
>
>
> ### What is the expected behavior?
>
> 1. According to AC: `If any of the mandatory fields are not filled and the user tap “Save” an inline error in the field where there is missing information.` I would expect to click on Save and get inline errors.
>
>
> ### Environment information
>
> **OpenProject version**
>
> **v.1.2.0-alpha (253)**
>
> **Operating System**
>
> * [ ] Windows
> * [ ] Mac OS X
> * [ ] Mobile iOS
> * [x] Mobile Android
> * [ ] Linux (please specify distro)
> * [ ] Chrome OS
> * [ ] Other (please specify)
* In all forms in the application, do not deactivate the "Save" button.
* If the user taps on the "Save" button but there are errors in the form, trigger inline errors below the pertinent field.
* The inline errors might be:
* Mandatory field missing: "This is a mandatory field. Please, fill the required information".
* Wrong field format: "The information provided doesn't match the format of this field".
* Any other error: "An error occurred with this field. Please, try again later"
* Empty comment box: "It is not possible to add an empty comment".
* When an inline error appears, ensure that the view navigates to the place where the faulty field is displayed (e.g. when the field is in a tab of the work package form not opened).
* If there is more than one error, the user will jump from a faulty field to the next when tapping in the "Save" button.
>
> ##
>
> ### Steps to reproduce
>
> 1. Open a work package creation page
>
> 2. Don't fill in all mandatory fields and try to save
>
>
> ### What is the buggy behavior?
>
> * Save is disabled
>
>
> ### What is the expected behavior?
>
> 1. According to AC: `If any of the mandatory fields are not filled and the user tap “Save” an inline error in the field where there is missing information.` I would expect to click on Save and get inline errors.
>
>
> ### Environment information
>
> **OpenProject version**
>
> **v.1.2.0-alpha (253)**
>
> **Operating System**
>
> * [ ] Windows
> * [ ] Mac OS X
> * [ ] Mobile iOS
> * [x] Mobile Android
> * [ ] Linux (please specify distro)
> * [ ] Chrome OS
> * [ ] Other (please specify)