Legacy JSW Integration - Ability to push the close-alert action to the JSW team-managed project which has the resolution status other than "Done"

User Goal

In the current design, if it's integrating the Opsgenie with the Jira Software Team-managed project via the Legacy JSW Integration and the project has the resolution status other than the default value Done, Opsgenie will always fail to send the close-alert action to resolve the JSW issue ticket with the following error:

Could not send [closeIssue] action to Jira [JiraSoftware]. Reason: 400 Bad Request: [{"errorMessages":[],"errors":{"resolution":"Field 'resolution' cannot be set. It is not on the appropriate screen, or unknown."]}} 

It's because of the following reasons:

• The JSW Team-managed project doesn’t accept the field Resolutionwhen resolving the issue ticket via an API request.

• If the resolution status in the workflow of the Team-managed project is the default Done, Opsgenie will not carry the following structure within the body payload when sending the close-alert action via the legacy JSW integration.

{{"fields": {
"resolution":

}}}

• If the resolution status in the workflow of the Team-managed project is anything other than the default Done, Opsgenie will carry the aforementioned structure within the body payload when sending the close-alert action via the legacy JSW integration. Reference → https://github.com/opsgenie/oec-scripts/blob/7bfed7cc0766eb37d0c0c850efc586dbe194cab0/Jira/scripts/actionExecutor.py#L152

It would be great to update this mechanism because sometimes it's required to integrate Opsgenie with the Jira Software Cloud instance on another Atlassian Cloud Site.

Possible Solutions

Stop sending the aforementioned structure within the body payload when sending the close-alert action via the legacy JSW integration, regardless the resolution status has been changed to anything else.

Known Workarounds

The only way to around this is either the following:

1. Advise the customer to stay with the default resolution status, Done.

1. Advise the customer to spin up a new JSW instance on the same Atlassian site of this Opsgenie, restore the configuration and data to this new JSW instance and switch to using the new framework JSW integration on Opsgenie.