Project

General

Profile

Actions
Copy link

Bug #27064

closed

Change validation settings page has contradictory documentation

Added by Clark ANDRIANASOLO about 2 months ago. Updated 9 days ago.

Status:
Released
Priority:
2
Assignee:
Véronique HAYAERT
Target version:
Rudder plugins - 8.2
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Trivial - no functional impact | cosmetic
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
81
Name check:
To do
Fix check:
Checked
Regression:
No

Description

In documentation sections in the plugin settings page, there is first a section, which information contradicts with the one in the documentation of the change made in #24206 :
1. Be careful: a change request is created when at least one predicate matches, so an exempted user still need a change request in order to edit a node from a supervised group.
2. configuring the [supervised] groups below will have no effect on validated users (in the list above), but will apply to non-validated users, who will still need to create a change request in order to modify a node from a supervised group. (see #24206)

The documentation should be corrected, as the 1st one is not up-to-date

Files

clipboard-202507040917-bqx3l.png (61.4 KB) clipboard-202507040917-bqx3l.png François ARMAND, 2025-07-04 09:17

Related issues 2 (0 open — 2 closed)

Related to Change validation - User story #24206: We need an option to force validation of change requestsReleasedVincent MEMBRÉActions
Related to Change validation - Architecture #26906: Migrate the ChangeValidationSettings snippet from Scala/lift to ElmReleasedVéronique HAYAERTActions
Actions
Copy link
 #1

Updated by Clark ANDRIANASOLO about 2 months ago

  • Project changed from Rudder to Change validation
  • Subject changed from Settings page to Change validation settings page has contradictory documentation
  • Description updated (diff)
  • Priority changed from N/A to To review
  • Target version set to 8.2
  • Severity set to Trivial - no functional impact | cosmetic
  • UX impact set to I dislike using that feature
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Very Small
  • Priority changed from 0 to 82
Actions
Copy link
 #2

Updated by Clark ANDRIANASOLO about 2 months ago

  • Related to User story #24206: We need an option to force validation of change requests added
  • Related to Architecture #26906: Migrate the ChangeValidationSettings snippet from Scala/lift to Elm added
Actions
Copy link
 #3

Updated by François ARMAND about 1 month ago

  • Assignee set to Véronique HAYAERT
  • Priority changed from To review to 2
Actions
Copy link
 #4

Updated by Véronique HAYAERT about 1 month ago

  • Status changed from New to In progress
Actions
Copy link
 #5

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/848
Actions
Copy link
 #6

Updated by Véronique HAYAERT about 1 month ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #7

Updated by François ARMAND 23 days ago

Actions
Copy link
 #8

Updated by Félix DALLIDET 9 days ago

  • Status changed from Pending release to Released
  • Priority changed from 82 to 81

This bug has been fixed in Rudder plugin change-validation v8.3.3-2.4

Actions
Copy link

Also available in: Atom PDF