...

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

This is the Custom Field that the value will be added to.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. 

Field Value Type

This is the The type of value that should is going to be addeddefined. Current options   Options are:

1. Simple Text Value - This will simply add the Value within the Custom Field.standard static values

2. Velocity Scripted Value - This allows you to create a Velocity condition that is used to determine the value. e.g. based on the sender email.

Value

...

1. uses Velocity Template Language (VTL) script to render dynamic values

2. Script Value - uses JavaScript to render dynamic values

Value

If the selected field value type is Simple Text Value, then the static value(s) will be entered here.  If the value type is Velocity Scripted Value, then the VTL script will be entered here. If value type is Script Value, then the JavaScript will be entered here.

Apply Rule

This is used to determine when the Custom Field Default should be applied. Current options are:

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.

For more info see:

1. Velocity: Velocity Script Custom Field Defaults

2. JavaScript: JavaScript Custom Field Defaults - Since 4.1.14

Inheritance of Custom Field Defaults

Custom field defaults are inherited in the project mapping hierarchy.  Defaults created on a default project mapping are inherited by other non-default project mappings.  Defaults created on a standard project mapping are inherited by that project mapping's children (mapping rules).  To override an inherited default, simply add a new default for that custom field at the current mapping level.

If a custom field default is set to apply only on comment, a default for the same custom field on the parent mapping level on create will still be inherited. The same behaviour applies in the opposite scenario.

...