In version 2.0 we changed default configuration location. Now you can configure plugin on Connection page in top side bar.
Connection security settings, API token for every connection
This update allows you create issues in Jira by using AC endpoint with API key, that configured in Connection Security settings. A primary use case for API token is allowing creating incidents using this key as X-API-Key parameter in request header.
Simple example of POST request for creating new incident/alert via Alert Catcher.
We introduce you Connection type - simplest feature to integrate your Jira with remote monitoring service.
Connection type defines a remote system which Jira integrate with.
It's a tiny interface, that allows you import all rules(triggers) into Jira:
After importing rules you can configure actions for problem creation and set assignee for every rule.
This feature allows you to close/acknowledge alert that came from external system. You should add Acknowledge alert post function to workflow transition. In example above, when you transition issue to status Done, alert from remote system should be acknowledged.
Close related incidents when problem closed
If you configured Rule actions and after a hardware failure, many incidents were created that caused the problem. After some time, you resolved the problem and you need to close all incidents related.
In release 2.0, we added the function of assigning incidents a certain status.
You need to set up a workflow alert and add the Transition Linked Issues (Alerts) post function to workflow transition. In the settings you need to specify the target status for your incidents.
In the example above, when the incident changes to the Resolved status, all incidents will be transferred to the Closed status.
HTTP multipart request
Now you can create incidents in Jira using HTTP multipart requests. This case may be useful when you integrate your Jira instance with systems like PRTG Paessler.