This could be possible by configuring the Jira Service Desk integration via Marid.
With marid, the flow will be Opsgenie -> Marid -> JSD. That way, you can edit the script in marid to be able to assign issues to the respective "Tech" in JSD via Jira API when marid receives the acknowledged action from Opsgenie.
Our default Jira Service Desk integration does not map acknowledged -> assign user, but when you select the option to send via Marid, you can really achieve any sort of custom mapping you want, as long as it's possible to achieve via Jira API. Hope this helps!
Hi Rob - yes, we do have some feature requests to be able to map more actions between Opsgenie and JSD by default. So hopefully in the future some of these will be implemented so this flow of acknowledgment -> assign issue can be achieved in the integration settings itself without marid.
Rob - this is already possible by adding the url of your Jira instance into the fields in the integration and concatenate the issue key field. Here is a screenshot indicating how to do so. In my example, the jira url is https://samirdemo.atlassian.net/browse/ and then I'm just adding the issue key field to the end of it. So each time an alert is created in Opsgenie from a Jira alert, it will add the link to the ticket for example https://samirdemo.atlassian.net/browse/ISD-70 (where ISD-70 is the issue key that is added to the end of that url to create the link)
We are using JSD -> Opsgenie -> JiraOps.
Short answer (for ppl looking to see if this Opsgenie is the right tool for them) - I would NOT recommend using Opsgenie, maybe in a few years but in its current form the product is not mature for Production use and the support from Opsgenie is nonexistent.
Priority Structure: Opsgenie has a priority structure that is different from Jira and the mapping doesn't work. If you are looking at Opsgenie because you are heavy jira user, consider another solution.
Integration - The way the integration works right now is that you can only alert to one team. We have multiple teams supporting various components, we had to hack the solution to get it to work. The integration is not ready for production use.
Support - No support available, the documentation is incorrect. You are essentially on your own.
Hi @Ali Khalidthanks for your feedback. I want to clarify for users that support for Opsgenie is available; on this very thread you can see a member of our team helping a user, and I see you also have a ticket open with the support team who are also working with you. So saying there is "no support available" is factually incorrect.
That being said, if you see errors in the documentation, please do let us know so we can correct them.
Just to chime in here...the support I have received to date has been excellent and I have been working in customer support since the 80s. I would agree that the integration between OG and Jira SD is not yet fully mature....but I believe the only way they get there is by providing good detail driven feedback that will allow them to make the needed changes required to reach that maturity. My $.02
Any update on
we do have some feature requests to be able to map more actions between Opsgenie and JSD by default. So hopefully in the future some of these will be implemented so this flow of acknowledgment -> assign issue can be achieved in the integration settings itself without marid.
It doesn't seem possible to do some basic things like automatically assign the OpsGenie responder to the JSD Incident that triggered the alert
We’re excited to announce the latest enhancement to Opsgenie’s Incident Investigation view. Now when an incident occurs users can select the previous stable deployment, and begin the redeployment pro...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events