Like many others, we use SSO to login to Atlassian. Are there any alternatives for an OpsGenie to JIRA integration that does not make use of an API token associated with a JIRA user account? This seems like bad practice and presents several challenges including: * If the user who generated the API token leaves and is disabled then the integrations stop working * The issues created in JIRA / JSM are show the user as the issue reporter and so they get notifications anytime an issue is created or updated. (suggestion so far from support is to use an automation to change the reporter, but i think that only partly solves the issue). It seems like this should be treated like a first party app integration that uses either some form of client credentials token or something similar. If there isn't an alternative solution for this today, how do I go about bringing attention to this in the form of a feature request or something like that?

Hi Jeremy, I will be happy to add your organization to this feature request. Can you please provide me with either the name of your organization or the Atlassian site that you belong to so that I can have you added? Thanks, Skyler

I would also like to have my organization added to this feature request. Thank you

Hello Julia, Sure thing, I have added your organization to this feature request as well. The ticket number is the same as mentioned previously in this thread for your reference. Best regards, Skyler

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OpsGenie to JSM integration without an API token - feature request

Cameron Gocke

Like many others, we use SSO to login to Atlassian. Are there any alternatives for an OpsGenie to JIRA integration that does not make use of an API token associated with a JIRA user account? This seems like bad practice and presents several challenges including:

If the user who generated the API token leaves and is disabled then the integrations stop working
The issues created in JIRA / JSM are show the user as the issue reporter and so they get notifications anytime an issue is created or updated. (suggestion so far from support is to use an automation to change the reporter, but i think that only partly solves the issue).

It seems like this should be treated like a first party app integration that uses either some form of client credentials token or something similar.

If there isn't an alternative solution for this today, how do I go about bringing attention to this in the form of a feature request or something like that?

Accepted answers

All comments

Skyler Ataide

Hi Cameron,

Thank you for your valuable feedback! Since your team utilizes SSO to login, you need to generate an API token and use this token as the password in the integration settings password field. Currently, there are not any alternatives for an Opsgenie to Jira integration that does not make use of an API token associated with a Jira user account in this case. If you would like, I can raise this feature request on your behalf. Hope this helps, please let me know if you have any further questions, comments, or concerns.

Thanks,

Skyler

Cameron Gocke

Yes I think a feature request would be most appropriate. A user level token isn't an ideal integration method for a first party application integration like this.

Skyler Ataide

Hi Cameron,

I wanted to inform you that I have submitted a feature request for this issue. I've added your organization to the internal ticket we have. For your reference, the ticket number is OGS-4032. You can reach out to us and reference that number in the future if you're looking for updates.

Best regards,

Skyler

Julia Foden

Hi Skyler

Can I also vote for / watch this feature request please.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

api

opsgenie

token