Project

General

Profile

Actions
Copy link

Bug #3151

closed

Clone Rules doesn't always include list of Directives

Added by Jonathan CLARKE almost 12 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
2.5.0~rc1
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I encountered a weird situation that I don't quite understand... So here are the detailed steps that I followed:

  1. Create a new rule A
  2. Add a Directive D to this Rule, and save. Don't add any groups.
  3. Clone rule A to a new rule named B, change the description.
  4. Notice that the list of Directives includes D, as expected.
  5. Look at the Event logs under Administration at the event that is "Added Rule B", and notice that Directives: is empty (that is, the empty string, not "None") (!!)
  6. Go back to Rules screen, notice that the table lists Rule B as having no Directives (!!)
  7. View details of Rule B, and clone it to Rule "Copy of <B>" (this is the default name for a cloned Rule). Don't change any of the parameters.
  8. Look at the Event logs under Administration at :
    1. the event that is "Added Rule B", and notice that Directives: is now "None" (!!)
    2. the event that is "Added Rule B", and notice that Directives: is empty (that is, the empty string, not "None") (!!)
  9. Go back to Rules screen, notice that the table lists Rule C as having Directive D (!!)

Something FISHY is definitely going on here...

Actions
Copy link

Also available in: Atom PDF