...
Let's get familiar with the Pattern syntax in Basic Mode.
The pattern must always contain the string "{value}" in Basic Mode.
Pattern may optionally contain a prefix and/or a suffix
The plugin uses regex matching in the backend. Based on prefixes and suffixes tries to pick the relevant string from the Source Field.
The "{value}" string part will be identified and populated to the corresponding custom field
If a suffix is not provided, then only the current line would be matched. By providing a suffix you may match multi-lines.
Casing and space chars in prefix/suffix need an exact match with the Source Field.
It is okay to add multiple mappings for the same Custom Field. You may leverage this to handle Casing/Space chars.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Please note, only if the comment input field (Comment/Description/Rich Text fields) 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. |