Can Opsgenie be set up to create Jira Issues in different Jira projects based on a selection in Opsg

Question

We would like Opsgenie to create Jira Issues.  However, in our Jira configuration we use the term 'project' to be synonymous to 'team'.  So each team has a Jira 'project'.  Our On Call members are in different 'Jira Projects'.  So at any given point in time the Opsgenie incident may need to go to a different 'project' in Jira.

In reading the configuration document it looks like only one Jira 'project' is defined.

Can this be done and if so how?

Thank you

Melissa

Stephanie Bryant · Answer

Ah, but I do want to create another issue, into a different jira instance. Company A and Company B.

Jira for Company A -> OpsGenie -> Jira for Company B.

Jira for Company B -> OpsGenie -> Jira for Company A.

Does that make sense?

I think I can solve for a looping issue using filters, but I can't figure out how to get OpsGenie to know which ticket in the other company's Jira to update correctly.

Samir · Answer

Hi @Stephanie Bryant - You can set-up filters on the Jira integration to specify which Opsgenie alerts should create/update issues in Jira.

When an alert is created from a Jira issue, the alias will be the issueKey of that Jira issue. So I would think you don't want another JIra integration to create a duplicate issue from that alert, right? That would create a looping effect, i.e. Jira issue created -> Opsgenie alert  created -> Jira Issue created

Can you reach out to support via support.atlassian.com so we can work with you on your workflow you're trying to achieve?

Thanks,

Samir

Stephanie Bryant · Answer

@Samir That mostly works. However, getting the jira tickets in two different instances is proving challenging. The alias is set to the issue ID by one of the integrations, and the other integration will create an issue from the OpsGenie alert, but will not update it (when closing the alert, or adding notes/comments, for example).

Any advice? I know this is a very old thread.