Allow the affected services field in Jira Ops to determine the OpsGenie service an incident is created with.

This suggestion applies to the following OpsGenie configuration:

When an incident is raised in Jira, create an OpsGenie incident and link them together.

Problem

In the OpsGenie configuration, there is no way to set the OpsGenie service from the Jira Ops 'affected services' field.

If you try to pick 'Components' for example, this will not work as the created issue will not have any components set.

The incident will fail to create with a warning visible in OpsGenie logs.

Suggestion

Allow the Jira Ops 'affected services' field to automatically set the OpsGenie service when the issue is created.

Workaround

The user must manually pick the service that all OpsGenie incidents will be created with, in the OpsGenie configuration.