Hide Forgot
The rules engine will supply a warning when you attempt to edit a flagtype that is used by a rule. This error seems to be given when it shouldn't be given (see attached RT) I think it is detecting that the flagtype matches a regex in the rule search condition. It should probably only supply a warning if the flag is explicitly used as a match or update condition
Instead of removing the warning, we'll just update the warning to be a little clearer. Changing a flag type of a custom field match won't cause the rules engine to throw the kill switch. It will only affect how the rule matches flags.
Tested on QA environment(5.0.3-rh19) Result: Pass Steps: 1.The warning message changed to: WARNING: This flag type is currently used on the following Rule Engine rules. Certain changes (like changing the name, category, requestability or the active state) may cause the rule to not match, or the Rules Engine to stop. Note that 'custom field' rule matches will not cause the Rules Engine to fail, but could cause the rule to stop matching.
Tested on QA environment(4.4.12065-1.el6) Result: Pass Steps: 1.The warning message changed to: WARNING: This flag type is currently used on the following Rule Engine rules. Certain changes (like changing the name, category, requestability or the active state) may cause the rule to not match, or the Rules Engine to stop. Note that 'custom field' rule matches will not cause the Rules Engine to fail, but could cause the rule to stop matching.
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.