Page Comparison

1. Content

...

• Click Edit button and set up a connection to USU and activate default interfaces. It is possible to set up more Interfaces as active at the same time.

• USU URL: http://[HOST]/vmweb/services/api/execwf

• USU Password is encrypted by runCrypto.bat (from USU).

• External User is the user name of the Jira User which is set in the Target System of the Generic Interface in USU. Otherwise the interface calls may be looped.

• After you have saved the configuration by clicking on Edit button, you can use the button Test Connection to verify the configuration.

• If you want to copy an interface including the mappings, just rename the default interface. The current Default interface will be saved with the new name. At the same time a new Default interface will be created with the default settings (as inactive).

• Create an external Jira user in Jira (go to 4.1.2).

• Create custom fields in Jira (go to 4.1.3).

4

...

There are more options how the Model Tickets and Cis in the Connector’s tables can be referenced from a Jira Issue. We recommend using Script Runner for that (made by Adaptavist, tested with version 8.2.1).

Here are the steps needed for creation of the references to Model Tickets and Cis:

• Create Resource in Script Runner and make a Local Database Connection.

• Create two Database picker Fields in Script Runner (don´t forget to put created fields on Issue screen):

  • Field Name: USU System-CI; Type: Database picker.

  • Field Name: USU Model Tickets; Type: Database picker.

• Create two Jobs in Script Runner.

  • Custom Scheduled Job for System-CI.

  • Custom Scheduled Job for Modeltickets.

• Fill in the tables according to your needs (there are examples how to set up a scheduler) .

• Copy and paste the script bellow to Inline Script Table and set up a new URL.

import groovy.json.StreamingJsonBuilder

def authString = "Bearer [Personal Access Token]".getBytes().encodeBase64().toString()

def body_req = '''{
"eventTypeName": "runObjectMapping",
"objectMappingName" : "System-CI"
}''';

URL url = new URL("http://.../jira/rest/SITVmConnectorBackend/1.0/SITVmConnectorBackend");
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("POST");
con.setRequestProperty("Authorization", "Basic ${authString}");
con.doOutput = true;
con.setRequestProperty("Content-Type", "application/json");
//con.outputStream.withWriter("UTF-8") { new Streaming JsonBuilder(it, body_req)}
con.getOutputStream().write(body_req.getBytes("UTF-8"));
con.connect();

println("url: " + url);
println("Content>:" + con.getContent())
println("ResponseCode:" + con.getResponseCode())
println("getResponseMessage:" + con.getResponseMessage())

con.disconnect();

• You can do the Script for Model Tickets (we recommend to create a New Job for it) in the similar way.

4.1.6 Internal/External Comments Feature

If information about how was the comment created in Jira was shared (internally or with Custumer), we need to set the following

• Add new Field map to Comment-Ticketdesc mapping

...

• Add new Object Field propertiesString to Jira Issue Comment (Jira Objects)

...

• Add new Object Field propertiesString to Ticket Description (USU Objects)

...

.1.6 Internal/External Comments Feature

If information about how was the comment created in Jira was shared (internally or with Custumer), we need to set the following

• Add new Field map to Comment-Ticketdesc mapping

...

• Add new Object Field propertiesString to Jira Issue Comment (Jira Objects)

...

• Add new Object Field propertiesString to Ticket Description (USU Objects)

...

4.2 Configuration of Script Runner

There are more options how the Model Tickets and Cis in the Connector’s tables can be referenced from a Jira Issue. We recommend using Script Runner for that (made by Adaptavist, tested with version 8.2.1).

Here are the steps needed for creation of the references to Model Tickets and Cis:

• Create Resource in Script Runner and make a Local Database Connection.

• Create two Database picker Fields in Script Runner (don´t forget to put created fields on Issue screen):

  • Field Name: USU System-CI; Type: Database picker.

  • Field Name: USU Model Tickets; Type: Database picker.

• Create two Jobs in Script Runner.

  • Custom Scheduled Job for System-CI.

  • Custom Scheduled Job for Modeltickets.

• Fill in the tables according to your needs (there are examples how to set up a scheduler) .

• Copy and paste the script bellow to Inline Script Table and set up a new URL.

import groovy.json.StreamingJsonBuilder

def authString = "Bearer [Personal Access Token]".getBytes().encodeBase64().toString()

def body_req = '''{
"eventTypeName": "runObjectMapping",
"objectMappingName" : "System-CI"
}''';

URL url = new URL("http://.../jira/rest/SITVmConnectorBackend/1.0/SITVmConnectorBackend");
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("POST");
con.setRequestProperty("Authorization", "Basic ${authString}");
con.doOutput = true;
con.setRequestProperty("Content-Type", "application/json");
//con.outputStream.withWriter("UTF-8") { new Streaming JsonBuilder(it, body_req)}
con.getOutputStream().write(body_req.getBytes("UTF-8"));
con.connect();

println("url: " + url);
println("Content>:" + con.getContent())
println("ResponseCode:" + con.getResponseCode())
println("getResponseMessage:" + con.getResponseMessage())

con.disconnect();

• You can do the Script for Model Tickets (we recommend to create a New Job for it) in the similar way.

4.3 Configuration of USU Service Management Package (Valuemation)

...