Versions Compared

Old Version 3

changes.mady.by.user Michael Eicks

Saved on

compared with

New Version 4

changes.mady.by.user Michael Eicks

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this section, you configure field mappings.

Currently the following field types can be mapped for creation and synchronization type-aware:

  • Text Field (< 255 characters)
  • Free Text Field (unlimited text)
  • Date/Time
    • Supported target OTRS format <YYYY-MM-DD hh:mm:ss> only, means: It is possible to map JIRA text fields to OTRS date/time fields if their value comply with the format
    • Empty field allowed
  • Date 
    • Supported target OTRS format <YYYY-MM-DD hh:mm:ss> only
    • Empty field allowed
  • Single Select List
    • Mapping depending on the key not the value
Multiple Select List fields in JIRA as well as components and versions will be transferred as comma separated lists to text fields in OTRS.

 

Note

Mappings for JIRA fields that do not exist will be ignored. Mappings for OTRS fields that do not exist will throw exceptions.

Warning

 Mapping of other field types is undefined and should be tested before using in production.

 

To add a field mapping, do the following:

  1. Select Add field mapping.
    The "Add Mapping" dialog is displayed.
  2. Enter the following information:
    1. JIRA Field Name: Name of the JIRA field that is mapped.
      Whenever the OTRS ticket is updated the current value of the JIRA field will be used to update the OTRS field.
    2. OTRS Field Type: Type of the OTRS field that is mapped.
    3. OTRS Field Name: Name of the OTRS field that is mapped.
    Click Save.
    The new mapping is displayed in the list.
Note

If you want to map the assignee of the JIRA Issue to OTRS you need to make sure that an OTRS user with the same name exists. Otherwise you can specify a ORTS User with the name "-".

To edit a field mapping, select Edit at the right of the field entry.

...