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

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Could not send action [resolveIssue] to JiraServiceDesk from Opgenie


Hello everyone, please your help,

I currently have Opsgenie integrated with Jira, it was working fine.

Now it only allows adding comments from Opgenie to JSM and vice versa, but when I want to close an alarm from Opsgenie the issue is not closed in JSM, when I close the issue from Jira the alarm is closed in Opsgenie.

When closing the alarm in Opsgenie, it reflects the following error:

Could not send [resolveIssue] action to JiraServiceDesk [XXX]. Reason: The issue does not have a "Resolve the issue" option or the issue you are trying to close does not exist so the "Close alert" action is not posted

Captura de Pantalla 2022-12-21 a la(s) 15.22.23.png

Please your help community.


5 answers

2 votes
Nick H Atlassian Team Dec 21, 2022

Hi @Silvia Llumiquinga ,

That error typically indicates the Resolved status is not available on the project integrated with Opsgenie. 

Within JSM - navigate to the Settings menu → Issues tab → Workflows → Edit the Project’s Workflow that needs mapped to Opsgenie action:




Click: +Add Status → search/select for status (Ex: Resolved) → enable: Allow all statuses to transition to this one → click: Add






Then Publish Draft, and retest if possible.


Sometimes the Resolve status may already be available on the project - but the workflow requires the issue to transition into another status prior. Allowing all statuses to transition to Resolved should resolve the issue.


^ If that's the case, I do understand it may alter your project's workflow, but if you can test it would determine if that is in fact the issue.

Hi @Nick H ,

Reviewed and made the change suggested by your previous comment, however we still have the same issue.

Maybe some other option??

Captura de pantalla 2022-12-27 a la(s) 19.29.20.pngCaptura de pantalla 2022-12-27 a la(s) 19.31.34.png


Attach the added status in Workflow


We tried add the "RESOLVED" state , but the error is the same

Nick H Atlassian Team Jan 04, 2023

Hi @Silvia Llumiquinga and @Xavier Uquillas ,

Under this project, can you please create a test issue and try to transition it to the Resolved status immediately after it's created? This would determine whether or not the issue can in fact be transitioned at any status.

I would also try testing transitioning the issue to Resolved from other statuses after it's created as well. Again - this might help narrow down whether or not your workflow allows for an issue to be moved to Resolved, and not have to transition to another status before this.

@Nick H

Created a test issue in Jira and it went to resolved status and if it works.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events