...
Let's get familiar with the pattern syntax..
- The pattern must always contain the string "{value}"
- Pattern may optionally contain a prefix and/or a suffix
- The plugin uses regex matching in the backend. Based on prefix prefixes and suffix suffixes tries to pick the relevant string from the Comment.
- 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 comment.
- It is okey okay to add multiple mappings for the same Custom Field. You may leverage this to handle Casing/Space chars.
Lets Let's look at an example to see the plugin in Action
Imagine we have added a pattern mapping as shown below:
Now let's add the following Sample Comment to the Jira Issue:
...