Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,467,937
Community Members
 
Community Events
177
Community Groups

Adding comment in Jira Service Management, when alert is acknowledged in OPSGENIE

Hi Community, 

Webhook in JIRA is set and integration in OPSGENIE as well. 

Alarm is created correctly in OPSGENIE when a critical incident is created. 

However, when acknowledged a comment is not added in JIRA even though this is set. 

Log from OPSGENIE below

According to the log is seems to be a permission or bad password issue. 

[system] Could not send [addComment] action to JiraServiceDesk [IT_Service_Desk_Jira Service Management]. Reason: 401 Unauthorized: [Basic authentication with passwords is deprecated. For more information, see: https://confluence.atlassian.com/cloud/deprecation-of-basic-authentication-with-passwords-for-jira-and-confluence-apis-972355348.html ]

2021/10/29 10:24:45.562

JSONRaw
Object

 

 

In OPSGENIE integration, I have added my personal account and password. 

Could this be the problem. Should it be a system account with special permissions I should add here?

 

Theis 

1 answer

1 accepted

0 votes
Answer accepted
Nick H Atlassian Team Mar 16, 2022

Hi @Theis Joergensen ,

That error can usually be corrected with using an API token in the password field of the integration here:

token1.jpg

 

In JSM click into your profile icon → ProfileManage your accountSecurity tab → Under the API Token section, click: Create and manage API TokensCreate API token → Name token something like “Opsgenie” → click: Create → click: Copy to clipboard → paste API Token into the integration's Password field → Save the integration

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events