Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,555,948
Community Members
 
Community Events
184
Community Groups

Opsgenie NOTE not being passed to JSM (error) Reason 401

Edited
Randy Everett
Randy Everett Aug 24, 2022

Can someone help?  The error is 7 pages and I've not been able to get it to stick and stay in this post. Here is a short start of the error. I can send the rest of the error message via email if that's allowed. Sorry, I'm a new opsgenie/jira user. 

Could not send [addComment] action to JiraServiceDesk [Jira Service Management]. Reason: 401 : "<EOL><EOL><EOL><EOL><EOL><EOL><EOL><EOL><EOL><EOL><EOL><html><EOL><EOL><head><EOL> <title>Unauthorized (401)</title><EOL> <EOL><EOL><EOL><EOL><!--[if IE]><![endif]--><EOL><script type="text/javascript"><EOL> (function() {<EOL> var contextPath = '';<EOL><EOL> function printDeprecatedMsg() {<EOL> if (console && console.warn) {<EOL> console.warn('DEPRECATED JS - contextPath global variable has been deprecated since 7.4.0. Use `wrm/context-path` module instead.');<EOL> }<EOL> }<EOL><EOL> Object.defineProperty(window, 'contextPath', {<EOL> get: function() {<EOL> printDeprecatedMsg();<EOL> return contextPath;<EOL> },<EOL> set: function(value) {<EOL> printDeprecatedMsg();<EOL> contextPath = value;<EOL> }<EOL> });<EOL> })();<EOL><EOL></script><EOL><script><EOL>window.WRM=window.WRM||{};window.WRM._unparsedData=window.WRM._unparsedData||{};window.WRM._unparsedErrors=window.WRM._unparsedErrors||{};<EOL>WRM._unparsedData["com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path.context-path"]="\"\"";<EOL>WRM._unparsedData["jira.core:feature-flags-data.feature-flag-data"]="{\"enabled-feature-

Answer
Watch
Like Be the first to like this
201 views

1 answer

1 accepted

0 votes
Answer accepted
Nick H
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 24, 2022

Hi @Randy Everett ,

That error looks like it might be related to your Jira instance - whether it is on-prem, DC, or not accessible to the internet.

If that's the case, we typically suggestion using the Legacy Jira integration, and configuring OEC.

With this, you would install the OEC service on a server, and it will sit in the middle of Opsgenie and Jira. Opsgenie alerts/actions would send to OEC, which will then execute a script to create the issue in Jira, add a comment, etc.

View More Comments
Randy Everett
Randy Everett Aug 26, 2022

Thanks. We are looking in to this to see if it will resolve the issue. 

Like
Reply

Suggest an answer

Log in or Sign up to answer
Opsgenie
Opsgenie
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

See all events