Given example blacklist:

[qMessagePattern:backtrace]
# QTBUG-63915
b2qt 64bit

[qMessagePattern:backtrace depth,separator]
# QTBUG-63915
b2qt 64bit

The blacklist tool will match qMessagePattern to the first item [qMessagePattern:backtrace]. Regardless of the action taken on the item, no option is provided to update other instances of qMessagePattern in the blacklist.

The tool should, at the outset, notify the user that there were multiple matches found, and request action on each.

Proposed flow:

• Multiple matches for ‘qMessagePattern’ found.
  • Examine matches, delete all, skip all

• Action on [qMessagePattern:backtrace] ?
  • Edit, delete, skip

• Action on [qMessagePattern:backtrace depth,separator] ?
  • Edit, delete, skip