Hey all, right now I have a very basic automation script that will edit the field values, of the "Create Issue" form from the Atlassian Jira Service Management Connector, and create a new issue. This is fine but there are a few potential issues and an additional feature I'd like to include. Any assistance would be appreciated 🙂
First, if anyone is in the process of creating an issue at the time that the automation script is triggered, the script will overwrite their values in the form. Is there a better way to create issues without editing the form fields and simulating a "create" button press? or would I have to bypass the connector and make a call to the jira API?
Secondly, I'd like to create a correlation rule to trigger the script on some alarm types on certain elements. Is there a way to pass data from the alarms to the automation script as parameter data (or otherwise)?
Thanks!
Hi Christopher,
As Felix mentioned, you can follow the documentation in order to parse the alarm that triggered the correlation rule.
In you automation script, you will have to retrieve the paramCorrelationAlarmInfo and parse all the fields as described in the documentation.
ScriptParam paramCorrelationAlarmInfo = engine.GetScriptParam(65006);
There is also a video you can follow to achieve this: Executing scripts from Correlation - DataMiner Dojo
Regarding the creation of tickets, the Jira Service Management connector already exposes a parameter (ID = 51) that you can set from the automation script to send creation requests directly Jira. This way you avoid overwriting parameter values that are available for users in cube.
What you will have to do in the automation script is to create the body of the request (see Jira documentation) and then set the JSON value in the parameter 51 of the element, which will forward the request to Jira API.
In addition, there is a public example on github (https://github.com/SkylineCommunications/SLC-AS-CorrelatedAlarm) for parsing an alarm from a correlation