Project

General

Profile

Actions
Copy link

Bug #22106

closed

Creating a global parameter doesn't trigger a policy generation

Bug #22106: Creating a global parameter doesn't trigger a policy generation

Added by Nicolas CHARLES about 3 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - Config management
Target version:
old 6.2 issues to relocate
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

editing it or deleting it does trigger the policy generation

Updated by Nicolas CHARLES about 3 years ago Actions
Copy link
 #1

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES

Updated by Nicolas CHARLES about 3 years ago Actions
Copy link
 #2

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/4579

Updated by Nicolas CHARLES about 3 years ago Actions
Copy link
 #3

  • Status changed from Pending technical review to Pending release

Updated by François ARMAND about 3 years ago Actions
Copy link
 #4

  • Fix check changed from To do to Checked

Updated by Alexis Mousset about 3 years ago Actions
Copy link
 #5

  • Subject changed from Creating a global parameter doesn't trigger a policy generation in Rudder 6.2, 7.1 and 7.2 to Creating a global parameter doesn't trigger a policy generation

Updated by Alexis Mousset over 2 years ago Actions
Copy link
 #6

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: PDF Atom