-
Bug
-
Resolution: Fixed
-
Low
-
Severity 3 - Minor
-
Issue Summary
The new JSM integration framework has an option to set the request status to 'Done' in JSM when an action is taken in Opsgenie. However, a default JSM project doesn't have a 'Done' status and the request statuses are being set to 'Canceled'.
Steps to Reproduce
- Create a JSM integration with the new framework.
- Set an outgoing automation rule to set the request status to 'Done' if the alert is closed in Opsgenie.
- Create a JSM issue.
- Close the corresponding Opsgenie alert.
Expected Results
This should set the status to 'Done', or even return an error if there is no 'Done' status. With the flexibility of the new framework, I'd almost expect you to be able to select any status that your project has when setting up the automation rules.
Actual Results
The JSM request is set to 'Canceled'.
Workaround
Add a 'Done' status to the workflow for the project and issue type.
[OPSGENIE-359] Closing an Opsgenie alert doesn't set the JSM request to 'Done' with new framework
I would also suggest more options for when an alert is closed in Jira, for example with the current integration this will allow my team to automate ticket creation for alerts and essentially live in Jira.
If the team cancel a ticket in Jira it should close the alert in opsgenie and add comment to state ticket cancelled thus alert closed. Just something to consider thanks again for the great products.
So what I did to correct this was change the workflow, removing Completed and replacing with DONE. Then I also had to remove the transition from Open to Cancel since for some reason every ticket would default to cancel. After these changes can now close tickets in opsgenie, and the reverse close alerts from Jira.
Cheers Chris
The problem is fixed.
Thanks!