View Source

For catWorkX OTRS Integration for JIRA it is recommended to create at least the following fields:

Field Name (Examples)	Field Type	Description
OTRS Ticket ID	Text Field (read only)	Name must match the value of the `OTRSKEY`
OTRS Customer	Select List (single choice)	If you want to create OTRS tickets from JIRA issues only via the "Create OTRS ticket" action, this custom field can be of type "text", "select list" or "SQL field" (additional add-on necessary)
OTRS Queue	Select List (single choice)	if you want to create OTRS tickets from JIRA issues via the Create OTRS ticket action'): can be fields of type text, select list or SQL field (additional plugin necessary

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

a custom field for storing an OTRS customer (Type: Select List (single choice)) and an OTRS queue (Type: Select List (single choice)) (if you want to create OTRS tickets from JIRA issues via the Create OTRS ticket action'): can be fields of type text, select list or SQL field (additional plugin necessary)
in the OTRS a dynamic field for the JIRA Issue ID, this should have been created automatically during the installation of the OTRS plugin, its name ('JIRAIssueID') has to match the value of the 'JIRAKEY'
Specified fields in mappings on both sides
- Mappings for JIRA fields that don´t exist will be ignored
- Mappings for OTRS fields that don´t exist will throw exceptions

Depending on your business needs, you probably have to create some more custom fields for Project Portfolio Management for JIRA. For example:

To create a custom field, you have to do the following: