Project

General

Profile

Actions
Copy link

Bug #2662

closed

When updating a rule with a used name, it should failed

Added by Jean VILVER over 12 years ago. Updated over 12 years ago.

Status:
Released
Priority:
N/A
Assignee:
Jean VILVER
Category:
Web - Config management
Target version:
2.4.0~beta3
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Actions
Copy link
 #1

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 50 to 2.4.0~beta3
Actions
Copy link
 #2

Updated by Jonathan CLARKE over 12 years ago

  • Category changed from Web - Maintenance to Web - Config management

Fixing category, this is not in the Administration section.

Actions
Copy link
 #3

Updated by Jean VILVER over 12 years ago

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

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from Pending technical review to Discussion
  • % Done changed from 100 to 90

Jean, why did you create the method ruleExists in LDAPRuleRepository, that you don't use, when there were already a method nodeRuleNameExists that you use, and that does the same ?

Actions
Copy link
 #5

Updated by Jean VILVER over 12 years ago

It's a mistake, and it is fixed in f3ebba5de1c0160318dafb3f78718a1edfe239b4.

Actions
Copy link
 #6

Updated by Jean VILVER over 12 years ago

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

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from Pending technical review to Released
  • % Done changed from 90 to 100

Thank you Jean, this is correct. You could have set the % to 100 though

Actions
Copy link

Also available in: Atom PDF