Jira Service Management Specific Settings

This page contains all Jira Service Managament specific settings required to actually copy any portal settings, like e.g. request types, SLAs etc.

In case Jira Service Management is unavailable you may still change parameters here but they will be ignored when the post function is executed unless Jira Service Management becomes available later on (and vice versa).

Required information:

  • Copy Portal: Select to copy Service Desk Queues 

    This now requires the installed and enabled MyGroovy App.

    The MyGroovy App comes bundled with the catworkx Project Portflio Management App.

    I the MyGroovy App is deactivated or removed the Jira Service Management part will cease to work. It also may have other negative impacts on the catworkx Project Portflio Management App as a whole.

The options below do not exist anymore in Version 10 and newer and are kept only as a refernce:

  • Copy Request Types and Groups: (optional) Select to copy Service Desk project Request Types and Groups
  • Copy Queues: (optional) Select to copy Service Desk Queues
  • Copy SLAs: (optional) Select to copy Service Desk project SLAs
  • Copy Customer Permissions: (optional) Select to copy Service Desk project Customer Permissions settings

Field to function parameter mapping:

Missing Jira Service Management

In case Jira Service Management is not installed, not licensed or disabled the box shown on the right will be displayed in the workflow post function during the configuration.

Incompatible Jira Service Management

In case Jira Service Management version installed is actually incompatible with this Project Portfolio Management version the box shown on the right will be displayed in the workflow post function during the configuration. The mismatching version is displayed at the end of the box.

Missing MyGroovy App

In case the MyGroovy App is not installed or disabled the box shown on the right will be displayed in the workflow post function during the configuration.