If I don't want to use opsgenie to create JIRA ticket but still want JIRA and opsgenie communication
Asked by AksChopra:

For sending custom fields to JIRA we need to use OEC, I don't want to use OEC.

So I want to create a JIRA ticket from my logging platform Azure (which is sending alert to Opsgenie)but at the same time I want the same interaction between JIRA and Opsgenie

Now what are the fields I should send to JIRA in JSON payload from Azure so that it can communicate (like updating, commenting bidirectional) with OPSGENIE afterwards


Answers:
author: Samir
body: Hi [@AksChopra](/t5/user/viewprofilepage/user-id/3787337) - so you want the alerts in Azure to create issues in Jira, and then the Jira issue to trigger an alert to be created in Opsgenie?

If so - I'm not sure if Jira and Azure have any pre-built integrations, might be a better question for the Jira team. It looks like there is an Azure DevOps app in the marketplace - <https://marketplace.atlassian.com/vendors/1216751/azure-devops>...

But in terms of the Jira issue triggering an alert to be created in Opsgenie, that occurs by setting up the webhook in Jira, and adding a Jira integration in Opsgenie as detailed in <https://docs.opsgenie.com/docs/jira-integration>

OEC is only needed for Opsgenie to communicate *to* Jira.

comments: author: AksChopra
body: No I am already creating Alerts from Azure in Opsgnie

I can create JIRA tickets from Azure

But I want JIRA and opsgenie to interact and update bidirectionally afterwards


author: Samir
body: Gotcha - so it sounds like you have the Azure alerts creating both a Jira ticket \& an Opsgenie alert, and you want all 3 to be in sync when an update is made to one of them?

If so, the best way to do this would be to have Azure create the alert in Opsgenie, and Opsgenie create the issue in Jira. This will have Opsgenie sitting "in between" the Azure alert, and the Jira ticket, and Opsgenie will be able to keep the 3 in sync.

If you're using Jira server, and your Jira instance is *not* accessible over the internet, then you'd have to use OEC in order for Opsgenie to be able to communicate to Jira at all. If it is accessible over the internet, then you don't need to use OEC.

There wouldn't be a way to have Azure create the issue in Jira, and create the alert in Opsgenie separately, and then have all 3 be in sync. Opsgenie needs to be in the middle of the 2 in order to keep all 3 in sync. Otherwise, you could have the Azure alert and the Opsgenie alert in sync, but Opsgenie wouldn't be able to update the Jira ticket, unless opsgenie was the one that created the Jira ticket.

Let me know if that helps! And if you have more questions, feel free to come into support and we can work with you from there.

Thanks,

Samir


author: AksChopra
body: Thanks Samir for the Reply

However the issue is I want to send more fields to JIRA like components, country and assignee but Opsgenie does not support sending custom fields to JIRA. For that they have provided the option of using oec service but installing and hosting oec service at our server is difficult. So we don't want to use oec.

I hope you understand the issue. That is the reason I wanted to send the Alert and JIRA ticket from Azure to opsgenie and JIRA respectively and then wanted JIRA and opsgenie to synchronize afterwards.


author: Samir
body: Hi [@AksChopra](/t5/user/viewprofilepage/user-id/3787337) - Yeah it's not possible to modify which fields Opsgenie sends to Jira *without* using OEC. OEC allows you to modify the script that makes the request to Jira, so you can customize the request with whatever fields you want.

But just using the native cloud integration with Opsgenie and Jira without OEC doesn't allow you that same flexibility. We do have some improvements coming to that integration soon, that might offer some more flexibility with custom fields etc.

Thanks,

Samir