Let's get familiar with the pattern logic..
- The pattern must always contain a string "{value}"
- Pattern may optionally contain a prefix and/or a suffix
- The plugin uses regex matching in the backend. Based on prefix and suffix 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 can match multi lines.
- Casing and space chars in prefix/suffix need an exact match with comment.
- It is ok to add multiple mappings for the same Custom Field. You may leverage this to handle Casing/Space chars.
Examples :
Consider a user adding the Sample Comment below to :
| Random lines here; Emp Id=007 Role=Agent User Name=James Bond <age>32</age> More text here |
|---|
Based on the above mappings the following would happen:
- Custom field 'Full Name' is populated with value 'James Bond'
- Description is populated with the whole of the comment text. ( You may use this trick to maintain a custom field which stores the Last Comment added to issue
) - Number Field1 gets updated as '32'
- Text Field2 gets populated with 'Random lines here' as it comes before the suffix ';'
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.
You may cross check the Log messages from 'Comment Handler Logs' section to see the success / error logs
