Add more statuses to transition issues to within the new JSM / Jira cloud integrations

User Problem

The new JSM and Jira cloud integrations have limited statuses to transition to when an action is taken on an Opsgenie alert. 

The JSM integration only allows issues to be transitioned to Done, and the Jira integration only allows issues to be transitioned to In Progress and Done.

Suggested Solutions

Provide more statuses JSM and Jira issues can be transitioned to.

Current Workarounds

1) Use OEC with the legacy JSM and Jira integrations to map to specific issue statues. Although OEC is primarily used for on-prem instances, there are use cases like this where OEC may be needed for cloud instances.

With this, you would install the OEC service on a server, and it will sit in the middle of Opsgenie and JSM / Jira. Opsgenie alerts would send to OEC, which will then execute a script to create the issue in JSM / Jira. You can modify the OEC script to customize things such as configure it to transition a JSM / Jira issue to a specific status.

2) Add a comment to the JSM / Jira issue when an issue is ack'd, closed, etc. and filter on this comment with an automation rule to transition the issue to a specific status:

Reference knowledge base article: JSM/OpsGenie: Move Jira Service Management issue to a certain status other than Done when corresponding OpsGenie alert is acknowledged or closed