...
...
Managing Custom
...
Field Mappings
| Excerpt |
|---|
SIL™ custom field descriptors mappings are used to translate the custom field value into a valid SIL™ value. |
Most of them are already mapped to a certain descriptormapping, but there are certain of them that are not, because we cannot guess in advance the types of custom fields you are using in your installation.
For those custom fields that are not mapped to a descriptor, the default descriptor mapping is used. This does not guarantee that the descriptor mapping is the proper one for the field, but it will attempt to determine the correct type by looking at the basic values it manipulates. Keep in mind that this may not be enough. For instance, a custom field may be represented internally by a number, but its real meaning is minutes. We cannot offer that interpretation, unless a descriptor is developed for that custom field (remember Shannon's Theory of Information? data != information).
| Info |
|---|
Our team is available to add more descriptorsmappings. If you believe a descriptor mapping is really needed, let us know. |
To access the custom field descriptors page mappings page go to cPrime Plugins Configuration -> Custom Field DescriptorsMappings:
For known fields, descriptors are not configurable because we want to prevent accidental modification. However, for unknown custom fields, you may click the Edit button and set a real descriptor:
Factories (Custom Field
...
Mappings)
The following factories (custom fields descriptorsmappings) are bundled in by default. They act like translators, hence the notation Jira native type -> SIL™ Type.
...
| Note |
|---|
Each app may add its own factories. The system is pluggable, so anyone can write new custom field descriptors apps and add support to the SIL™ language for them. Don't be surprised if you see more descriptors. |
See also
...