Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,764
Community Members
 
Community Events
176
Community Groups

OpsGenie edge connector for Jira Cloud

Hello,
Currently we are using integration between OpsGenie and Jira SD via Opsgenie Edge Connector (OEC). We had to do it that way so we could work with priorities and tags/components.
Now there is plan to migrate to Jira Cloud so I would like to ask how we can continue using OEC so we could manage priorities and tags. We are also using tags to filter alerts which will get to Jira.
So basically I would like to know is handled functionality of OEC for OpsGenie/Jira Cloud integration.
Thank you

1 answer

1 accepted

1 vote
Answer accepted
Nick H Atlassian Team Mar 07, 2022

Hi @pavol_cvincek01 ,

You can continue to use OEC after the migration. Although OEC is primarily used for on-prem instances, we do see customers using it with their cloud instances to map Opsgenie alert fields to specific Jira / JSM issue fields.

We also recently released a new Jira and JSM integration framework that can map these fields - including some custom fields - out of the box without using OEC: https://community.atlassian.com/t5/Opsgenie-articles/NEW-Jira-Software-and-Jira-Service-Management-Opsgenie/ba-p/1952529

jiraoec.jpg

Hello @Nick H ,
It's great that you are taking care of those priorities. That's what we missed back then, together with tags/components. I have spent a lot of time with coding of the python script to make priorities and tags/components work for us.

So in case we would like to continue use OEC even for Jira Cloud what would be the solution?
Would be enough to update "/home/opsgenie/oec/conf/config.json" for oec.service? Currently we have Red Hat VM where Jira SD and OEC resides so after the migration to Jira Cloud, only OEC would remain and took care of the integration from OpsGenie to Cloud Jira.
Is that it or there is more to make it work?

Nick H Atlassian Team Mar 10, 2022

I believe that's the only thing you'd need to update for OEC. Unless your cloud instance moves to another server, that may need to be installed there too.

Hi @Nick H 
I thought that Jira Cloud won't need our own server to run. Something like we have it for OpsGenie. We don't have OpsGenie installed on our servers. So that means that Jira Cloud will be running on our own servers as it is now?
Thanks

Nick H Atlassian Team Mar 16, 2022

Hi @pavol_cvincek01 ,

OEC can realistically be installed on any server or machine. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events