Global settings improvements and protect against non-acknowledged changes
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
##### ISSUE TYPE
* Improvement Request
##### COMPONENT NAME
~~~
UI
~~~
##### CLOUDSTACK VERSION
~~~
4.17.*.*
~~~
##### SUMMARY
This request is for improvements for the "Global settings" screen.
1. As any user with correct privileges, Protect against "reset" button press without acknowledgement.
- On the "Global settings" screen there is no guard on the reset button.
- Clicking the reset button should prompt user. "Are you sure you want to reset "value" to "default value".
- Selecting the "Yes or Ok" button would update the value in the database with the default value.
- The "Cancel" button will close the prompt without changing any values.
2. As "Admin", the UI offers a way to update the default value stored in the database.
3. As "Admin", the UI offers an editable regular expression to test against, and enforce formatting for the value and default value.
4. As "Admin", the UI offers the ability to edit the description.
5. Any changes should be logged with before and after values.
6. As "Admin", the UI offers a way to update the "Category" field value.
Contributor guide
Research direction
Start at the Global settings screen and trace the existing reset action and administrator controls. Review how settings are persisted and changes are logged, then define completion as guarded resets plus editable default values, validation, descriptions, categories, and before-and-after audit entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100