...
| Warning |
|---|
In case you try to re-use an existing rule name, you would get a warning as shown below.
|
Field Parsing Logic
Let's get familiar with the Pattern syntax.
...
| Warning |
|---|
Please note, only if the comment contains Jira accepted field values it would be populated in the Custom Fields. Eg : Providing text field to a Numeric Custom Field, would fail to populate the Custom Field. Similarly for date field, URL fields etc.. Please visit "Supported Fields" section of the Documentation for more details. |
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
| Warning |
|---|
Please note: You won't be able to able to add multiple rules for the same 'Project' and 'Issue Type' combination. In case you try to add the same, system would prompt you whether you wish to overwrite the existing Rule. Clicking 'OK' would replace the previous rule with this new rule. Instead you may choose another Project/ Issue Type combination and proceed as well.
|
