|
It would be really great if someone from UX could go through FOLIO and file bugs for all the various inconsistencies regarding how things look when they are edited, how you edit, where delete option lives, what the save button says, whether there are save/delete confirmations or not, what the required field indicator looks like (asterisk w or without space), whether record last updated displays or not (in both view and edit) etc.
before I forget, let us make sure this happens for any Consistency Review issues on JIRA:
1. Apps are reviewed. Inconsistencies are spotted and documented.
2. We figure out how many occurrences of an inconsistency can be solved by updating central components, and how many require instance-specific implementation changes
3. We update UX documentation to reflect the official pattern, if relevant
4. We create issues for each occurrence, explaining how to make it consistent.
When issues like this get created in Jira, it would be great if 1) the styling is documented and current on the UX site and 2) the Jira issue includes a link to that latest styling on the UX site. That way, if other POs or devs for others apps are trying to ensure they are consistent, they can look for guidance in the Jira issues and follow the link to get the latest styling details.
If the form is dirty (fields have been edited), it would be best with a confirmation modal no matter how the changes are cancelled, since users may otherwise expect the changes to be there if they open the form again. If the form is clean, no modal is needed.
|