Guidelines for Adding Pattern Mappings

Rule Name :

'Rule Name' is used to uniquely identify each rule. Rule Name can not be duplicated.

Mode Selection (Basic / Regex)

We have provided two modes "Basic Mode" & "Regex Mode" to parse the field logic / pattern mapping.

Mode provides users with the flexibility to input data freely in Basic Mode or utilize regular expressions in Regex Mode. This empowers users to define patterns according to their preferences. The following guide outlines the process of mode selection, the Pattern Mapping dialog box, and validation procedures in both Basic and Regex Modes.

The highlighted yellow area represents the Mode checkbox, with unchecked indicating Basic Mode and checked indicating Regex Mode. Default mode is Basic, checking the box switches to Regex. Multiple mapping rows can be added.

                                                 Example for Basic Mode

In Basic Mode, users can freely input data within curly braces "{value}" into the Pattern Field.

                                                  Example for Regex Mode

In Regex Mode, users can utilize regular expressions in the Pattern Field. You can refer Regex Helper Module to know about how to validate your regular expressions.

Pattern Field Validation:

The data will undergo validation if the Pattern Field is either empty or contains invalid data. In such instances, the Pattern field will be visibly displayed in an orange color. This validation process applies to both Basic and Regex modes.

If the 'Pattern' field is empty or not in the expected format when adding a pattern mapping, a popup message appears at the top, highlighting the respective field for user attention and correction.

After carefully selecting all the fields and ensuring that the specified condition in the Pattern field is met, proceed to click on "Add Pattern Mapping" to observe the newly created rule on the 'Configure Comment Handler' page.

Rule Priority

What if we have multiple rules defined which a which might be applicable for a particular Jira Event. 

This comes into picture when you have rules defined for 'All Projects' and or 'All Issue Types' which are called 'Global rules' depicted with 'G'

Consider the four rules above. Imagine we are Creating a 'Task' in 'Business Project'.

Here even though all the rules match this Create Issue Event, the rule which is defined at the most fine grained level would take priority over Global Rule and would execute

Here the priority would be in the order : ddd > qqq > 111 > aaaaa