Actions
Enhancement #27043
open
Change request details history is not updated when updating via API
Pull Request:
UX impact:
It bothers me each time
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Name check:
To do
Fix check:
To do
Regression:
No
Description
When updating a change request in the UI (name/description), the change request history in the change request details page contains rows about some modification :
The page also refers to the last date of modification in the header.
But when updating the same change request using the REST API, such modifications are not reported in the page: event logs are not created.
Event logs should be created even when updating change requests using the REST API
Files
| clipboard-202506061010-01wrk.png (19 KB) clipboard-202506061010-01wrk.png | |||
| clipboard-202506061013-d2qav.png (89.2 KB) clipboard-202506061013-d2qav.png |
Updated by Clark ANDRIANASOLO about 1 month ago
It impacts #26904, which migrate the page to use the public REST API in 9.0, so until this bug is resolved the page will have the issue of not updating the header and modification/change history
Updated by Clark ANDRIANASOLO about 1 month ago
- Related to Architecture #26904: Migrate the ChangeRequestEditForm snippet from Scala/lift to Elm added
Updated by François ARMAND about 1 month ago
- Tracker changed from Bug to Enhancement
- Priority changed from To review to 2
- Target version changed from 8.2 to 9.0
- Severity deleted (
Minor - inconvenience | misleading | easy workaround) - Priority deleted (
73)
Updated by Clark ANDRIANASOLO about 1 month ago
- Assignee set to Véronique HAYAERT
Updated by Véronique HAYAERT about 1 month ago
- Status changed from New to In progress
Updated by Véronique HAYAERT about 1 month ago
- Status changed from In progress to Pending technical review
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/851
Updated by Clark ANDRIANASOLO 3 days ago
- Status changed from Pending technical review to In progress
This is a bug that could be addressed in between the alpha and beta phases of 9.0
Actions