Skip to main content
Version: V3.8

Flag Rules

Use Settings > Flags Config > Flag Rules to override the level of matching findings. When UI authentication is active, you need the Project Manager role to create, edit, disable, or delete these rules, including Ignore actions on an analysis's Flags page. With UI authentication inactive, those actions do not require a role assignment.

Rules persist across collections. They can assign Info, Warning, Error, or Ignored. Ignored flags remain in the analysis but are excluded from flag counts, scores, and default views. They can be inspected with the Ignored toggle on the Flags page.

Create a rule from an analysis​

  1. On the Flags page, choose the ban-icon button on a flag (tooltip Ignore this flag (create a flag rule)), or the one on its type row (tooltip Ignore all flags of this type (create a flag rule)). A flag that already has a rule shows Edit and Remove buttons instead.
  2. Choose This app only or All apps. App scope uses the app identifier and collection server together.
  3. Select the level. Ignore actions initially select Ignored, but you can choose another level.
  4. Add an optional comment explaining the exception, then choose Create rule.

An individual rule matches the flagged item's key. A type-wide rule matches every finding of that type. For custom flags, the rule also targets the specific custom flag definition.

Rule precedence​

QSDA evaluates enabled rules that match the flag and app:

  1. An item-specific rule wins over a type-wide rule.
  2. Among rules with the same item specificity, an app-specific rule wins over an all-apps rule.
  3. Without a matching rule, a built-in flag uses its Flag Levels default; a custom flag uses its definition's level. Warning is the fallback when a built-in default is unavailable.

For example, an all-apps exception for one item takes precedence over a type-wide rule limited to its app. Avoid overlapping rules with the same specificity so the intended result is clear.

Manage rules​

Select a row on the Flag Rules tab to Edit Rule or Delete Rule, or use Add Rule to author one directly. The rule dialog contains:

FieldPurpose
FlagFlag type the rule matches.
Custom flag ruleCustom flag definition the rule matches. Shown and required when Flag is Custom flag.
Item keyKey of the flagged item. Leave it blank to match every flag of the selected type.
App scopeApp id the rule applies to. Leave it blank for all apps.
Collection serverServer host the app was collected from. Shown after an app id is entered; supply it when restricting a rule to an app.
LevelLevel assigned to matching flags.
DescriptionReadable description of the rule shown in lists.
CommentReason the level is appropriate.
EnabledControls whether the rule is applied.

Creating a rule from an analysis fills these details for you.

A rule's matching target and app scope are fixed when editing it. Create a replacement rule if those need to change, then remove the old rule after checking the result.

Clear Enabled to suspend a rule without deleting it. If a custom flag definition has been removed, its associated rule is marked orphaned. Review and remove rules that no longer serve a purpose.

On the Flags page, a rule indicator identifies overridden findings, and a ban icon identifies ignored findings. Project Managers can edit the associated rule with the pen button or remove it with the ban-icon button (tooltip Remove the flag rule that applies to this flag). Deleting a rule allows a less-specific matching rule or the default level to apply. Level changes are applied to loaded analyses and their counts are refreshed.