Versions Compared

Old Version 5

changes.mady.by.user Michael Eicks

Saved on

compared with

New Version 6

changes.mady.by.user Michael Eicks

Saved on

Key

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

...

Note

The above config file is an example. Please change all relevant values, so it matches your environment. Especially remove the example mappings:

Code Block
# Mappings from JIRA fields to OTRS Text/Textarea/Dropdown fields
MAPPINGS=
# Mappings from JIRA Date/Time or Date fields to OTRS Date/Time fields
DATE_TIME_MAPPINGS=
# Mappings from JIRA Date/Time or Date fields to OTRS Date fields
DATE_MAPPINGS=

 

Necessary Fields 

The following fields have to be created if they didn´t exist already:

...

 

...

Mapping

  • To map JIRA fields to OTRS standard fields you can use the following fields names (they are also listed in the config file):

    Code Block
    languagenone
    titleKeys for OTRS standard fields
    collapsetrue
    queue
title
type
service
sla
state
priority
owner
responsible
customerUser
  • To map JIRA fields to dynamic fields the internal OTRS name has to be used.
  • For JIRA custom fields their name as well as their ID can be used in mappings

  • The following JIRA system fields can be used for mappings:

    Code Block
    languagenone
    titleKeys for JIRA standard fields
    collapsetrue
    summary
type
reporter
priority
description
key
status
assignee
resolution
votes
id
watches
project
timespent
timeestimate
timeoriginalestimate
created
updated
duedate
resolutiondate
security
environment
components
fixForVersion 
    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 "-". The mapping for that would be std_assignee,std_responsible.

...