Summary

Custom field defaults allow static or dynamic values to be defined for custom fields in an issue.  These values can be configured to be applied to an issue during issue creation and/or comment.  Field values are inherited, meaning for example that a value for a field set at the project mapping level will be inherited by all of that mappings rules, unless overridden at the rule level.

For further details and examples see: /wiki/spaces/JEMH/pages/143491123

Creating a Custom Field Default

1. Click New Custom Field Default. This will then create a new Custom Field Default with some example values.

   Image RemovedImage Added

2. Now press Edit. This will open the Custom Field Default editor.

   Image RemovedImage Added

3. Now select/enter relevant values for this Custom Field Default and press Submit to save the configuration:

   Image RemovedImage Added

4. Once the parameters of the custom field default have been defined as desired, click submit to save changes.  The newly configured default will be present in the list on the mapping:

...

Configuration Options

Custom Field

The custom field that the value will be used for.  If there is a project defined in the associated project mapping, then only fields applicable for the projects issue types will be shown. 

...

1. Create only

2. Comment only

3. Create and Comment

Setting Dynamic Values using Scripting

Within Custom Field Defaults you are able to create Custom Scripts which will allow values to be set based on the email content. Scripting can be used with either Velocity or JavaScript.

...