Actions
Bug #7536
closedMake possible to delete ANY active technique
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
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