Bug 1125270 - RFE: Show hierarchy for rules and groups when I select "Run after" while create or edit rule
Summary: RFE: Show hierarchy for rules and groups when I select "Run after" while cre...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Internal Tools
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-31 13:15 UTC by Rony Gong 🔥
Modified: 2014-08-01 01:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-01 01:28:56 UTC


Attachments (Terms of Use)

Description Rony Gong 🔥 2014-07-31 13:15:54 UTC
Description of problem:
RFE: Show hierarchy for rules and groups when I select  "Run after" while create or edit rule

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Go to the rule egine index page, create or edit a rule engine
2. Select value for "Run after",  so many rules list there
3. It is better that only list the active rules and Show hierarchy for rules and groups

Actual results:


Expected results:


Additional info:

Comment 1 Jason McDonald 2014-08-01 01:28:56 UTC
Note that the grouping of rules is just a cosmetic feature to make it easier for users to find what they're looking for in the user-interface.

Inside the Rules Engine, there is no hierarchy of rules based on the UI grouping.  Instead, there is a single flat 'master list' of rules containing all of the rules in Run After order.  The grouping of rules in the UI doesn't affect the Run After order and it is perfectly valid to mark a rule in one group to run after a rule from another group.

It is also valid to have disabled rules in the run order.  Those rules will be skipped when the Rules Engine processes bugs, and when the rule is enabled it will keep its place in the run order.


Note You need to log in before you can comment on or make changes to this bug.