Advanced compare with regular expression in the rule doesn't escape special characters automatically

XMLWordPrintable

    • Type: Bug
    • Resolution: Not a bug
    • Priority: Low
    • Component/s: Automation
    • None
    • Minor

      Issue Summary

      Using an If block having an advanced compare with regular expression fails to match string values if they contain special characters.

      Steps to Reproduce

      1. Create a rule
      2. Add an if block with advanced compare conditions to match a custom field if the value is equivalent to any one of the regular expression values.
      3. Create an issue, and set this customfield to a value that exists in the regular expressions that have a value with brackets.

      Expected Results

      • The condition should match based on the rule and any brackets should be auto escaped

      Actual Results

      • The conditions don't match because the value selected in this case has brackets which are not seen as a literal bracket.

      Workaround

      You can escape those special characters to ensure that the regular expression is matched with the rule.

      (Virtual|Disc|Tape|CPD|Peripheral|Business \(Process\))
      

        1. automation-rule.png
          43 kB
          Prince N

            Assignee:
            Unassigned
            Reporter:
            Prince N (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: