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

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

Melissa Thornton January 30, 2020

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


1 answer

1 vote
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 31, 2020

Hi @Melissa Thornton  - Each Jira integration can only create issues in a single Jira project. But you can setup multiple Jira integrations to create issues in different Jira projects. Are you going to be manually creating these Jira issues from Opsgenie alerts? Or do you want alerts in Opsgenie to automatically create an issue in Jira? If you could reach out to our support team thorugh the in-app chat, or by creating a ticket through the form here:


We can work with you to set it up to achieve your workflow.




Rick Hadsall June 17, 2020

@Samir  what about to multiple Jira instances in different sites?

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 17, 2020

Hi @Rick Hadsall - same idea, would just need to add a separate Jira integration for each Jira instance. each integration you add you specify the URL, issue type, project key, and username/password in order for Opsgenie to create issues through that integration.


So you can add multiple jira integrations with different Jira URL/Credentials in order to create issues in multiple jira instances on different sites. 

Stephanie Bryant December 3, 2021

@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.

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 4, 2021

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 so we can work with you on your workflow you're trying to achieve?




Stephanie Bryant December 7, 2021

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events