Project

General

Profile

Actions
Copy link

Bug #7536

closed

Make possible to delete ANY active technique

Added by François ARMAND about 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Vincent MEMBRÉ
Category:
Web - Config management
Target version:
2.11.17
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Currently, on several case (technique missing or more than one active techniques based on the same technique), you simply can not delete the technique, forcing to rely on LDAP voodoo. This is not a correct UX.

An user must always be able to remove an active technique, whatever the source problem - else, how could he correct it ?

Actions
Copy link
 #1

Updated by François ARMAND about 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/984
Actions
Copy link
 #2

Updated by François ARMAND about 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 9 years ago

  • Parent task deleted (#5829)
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.17, 3.0.12 and 3.1.5 which were released today.

Actions
Copy link

Also available in: Atom PDF