Page Comparison

...

Let's get familiar with the pattern logicsyntax..

• The pattern must always contain a the 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 If a suffix is not provided, then only the current line would be matched. By providing a suffix you can may match multi lines.
• Casing and space chars in prefix/suffix need an exact match with comment.
• It is ok okey to add multiple mappings for the same Custom Field. You may leverage this to handle Casing/Space chars.

Examples :

Image Removed

Consider a user adding the Sample Comment below to : 

...

Lets look at an example to see the plugin in Action

Imagine we have added a pattern mapping as shown below:

Image Added

Now let's add the following Sample Comment to the Jira Issue: 

Based on the above mappings the following would happen:

• Custom field 'Full Employee Name' is populated with value 'James Bond'Description is populated with the JIRA-ADMIN'
• 'Employee Address' field is populated with value '5th Floor, Tower ‘X’,Silver Enclave,Airport Road, Bengaluru'
• 'Total Score' field is populated with '7'
• 'Server URL' field gets updated as 'https://mgtechsoft.atlassian.net'
• The 'Actual Start Date' field gets updated as '25/Aug/22 10:55 AM'
• Lastly the 'Last Comment Field' 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 ';'

Image Removed

...

...

...

You may cross check the Log messages from 'Comment Handler Logs' section to see the success / error logs

...