Issue Summary

Support for untranslatedName or consistent status mapping in Opsgenie-Jira Service Management integration to avoid issues with user language settings

Steps to Reproduce

Currently, the Opsgenie-Jira Service Management (JSM) integration relies on the status name field when mapping or transitioning Jira issues based on Opsgenie alert actions. However, the name field is subject to translation based on each Jira user's language settings. This can cause integration failures when users have different language preferences, as the status name may appear differently (e.g., "Cancelled" vs. "Canceled" or other translations).

The integration does not support using the untranslatedName field, which remains consistent regardless of user language. As a result, customers must manually account for all possible status name variants, which is error-prone and not scalable.

Expected Results

• Add support for using the untranslatedName field in Opsgenie-Jira integrations, or

• Provide a mechanism to ensure status mapping and transitions work reliably regardless of user language settings.

Actual Results

Inconsistency when using different languages

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available