LMS-739 Redesign Amendment Information Panel
Feature request summary
Re-design the Amendment Information Panel so that it changes the way the information is updated/saved.
In order to do that, a ‘Save’ and ‘Cancel’ buttons (and perhaps ‘Previous’ and ‘Next’ too) should be added, and these ‘Save’ and ‘Cancel’ buttons become live/active only if the user makes a change.
If the Amendment Information panel changes (because the user made a change to a field) and the user moves the cursor in some way that will trigger a refresh (e.g. moves the cursor to a different amendment), then the system should (1) save the changes that have been made and then (2) refresh the document.
Also, whilst editing/updating the amendment information, other areas of the editor should be accessible and should not freeze.
Background
Currently, when an user edits any field in the Amendment Information Panel, the system waits around 5 seconds since the user stops typing and then updates the information accordingly.
This way of updating/saving information seems to be very cumbersome, getting in the way, and users do not appear to be satisfied with the overall experience. .
We thought that it would be best to redesign the Amendment Information panel so to give a better experience to users.
Differently from the Document Information panel (which is not used repeatedly by users but a couple of times when the information needs to be updated), the Amendment Information panel is used more frequently and therefore having a dialog box as proposed in https://lawmaker.atlassian.net/browse/LMS-737 could be a bit too disruptive. Therefore it might be better to apply a different approach, as the one proposed under ‘feature request summary’. An alternative approach would be to follow something like the Attributes panel, where the values are not initially editable, and the user has to click on the field to edit it and then click 'accept' to update the information.
Status | Feature logged |
---|---|
Lawmaker components affected | Amendment Lists, Amendments |
Raised by organisation(s) |
|
Planned version to be included in (if any) |
|
Related development ticket(s) |
|