Versions Compared

Key

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

...

Info

When the add-on is installed and no configuration file is found, there will be an error in the log file stating the exact path where the file is to be expected.

An example otrsintegration.properties configuration file is included in the .jar file inside the .obr file.

...

The same example is also

...

listed here: Example of otrsintegration.properties

In the otrsintegration.properties configuration file, you have to configure the following:

 

Config-File

 

You have to, e.g., specify the URL of OTRS and the login information.

...

Please find beneath a typical config file. Explanations to the config options are documented inline in the code block

 

 

Code Block
languagenone
titleotrsintegration.properties
collapsetrue
 

...

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

...

 

 

 

 

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.

...